topic Re: Possible Bug in Drive for Windows EXE Arguments. in Nuxeo Forum

Possible Bug in Drive for Windows EXE Arguments.

Bryce_Bolton — Thu, 23 Jul 2020 15:41:49 GMT

Using this tutorial https://doc.nuxeo.com/client-apps/how-to-manually-initialize-or-deploy-a-nuxeo-drive-instance/ I've installed Drive for Windows with the EXE variables below...

nuxeo-drive.exe /VERYSILENT /TARGETDRIVEFOLDER="%USERPROFILE%\Documents\Nuxeo Drive" /TARGETURL="http://localhost:8080/nuxeo" /TARGETUSERNAME="foo"

The TARGETURL has been modified to reflect our environment.

I've selected these variables so when we mass deploy the Drive application the user does not need to know and enter our Nuxeo url.

The issue I'm seeing is when you go to the Accounts settings page you see the Username as "foo" (or whatever you enter in the EXE argument).

Once you log back in, the "foo" name stays in the username field. It never changes to the actual username of the re-authenticated user.

It's only a visible issue and does not affect the operation of the Drive app, but it's one that could confuse our support staff if they need to troubleshoot and see a different name in the username field.

Re: Possible Bug in Drive for Windows EXE Arguments.

Mickaël_Schoent — Wed, 29 Jul 2020 15:54:40 GMT

Would it be possible that the username for Nuxeo is the same as the Windows one? I mean, instead of /TARGETUSERNAME="foo", that would be correct to use /TARGETUSERNAME="%USERNAME%".

Re: Possible Bug in Drive for Windows EXE Arguments.

Bryce_Bolton — Wed, 29 Jul 2020 16:35:33 GMT

Oh, never thought to try that... Ill give it a shot.

Re: Possible Bug in Drive for Windows EXE Arguments.

Bryce_Bolton — Wed, 29 Jul 2020 16:53:53 GMT

%USERNAME% did fix it and now shows the users name.

Re: Possible Bug in Drive for Windows EXE Arguments.

Mickaël_Schoent — Tue, 04 Aug 2020 13:19:20 GMT

I created NXDRIVE-2272 (Save username changes when updating credentials). It will be fixed in Nuxeo Drive 4.4.5.

Edit: the fix is included in Nuxeo Drive 4.4.5.