Re: Create background queue connection right after session starts
Thanks Martin!
Before posting, please read how to report bug or request support effectively.
Bug reports without an attached log file are usually useless.
You mention in https://winscp.net/tracker/1681 that the simultaneous creation of the background queue could be enabled with a hidden setting somewhere.
Is there anywhere I could find instruction on how to do this?
This is something I have wanted to do for a very long time.
Interface\QueueBootstrap=1
Hello there,
You mention in https://winscp.net/tracker/1681 that the simultaneous creation of the background queue could be enabled with a hidden setting somewhere.
Is there anywhere I could find instruction on how to do this?
This is something I have wanted to do for a very long time.
Is it possible to create both the connections beforehand(at the time of first connection creation)?
Since a user has already logged in to the remote server, therefore, I expect WinSCP not to ask the authentication again while doing file modification. If not possible for some reason, then, for the ease of users, WinSCP should use the already stored password and only ask for the token to be entered.
Files saved in an editor are put to a transfer queue for an upload. The queue (must) uses a different connection, so it needs a new authentication. WinSCP actually remembers the token (assuming it's a password) and re-tries it for the authentication. That fails (I assume the token is one-time only) and WinSCP restarts the authentication from the scratch, not using a stored password, as it does not know what caused failed authentication (which of the two "passwords"). Try turning off Remember password for duration of the session:
https://winscp.net/eng/docs/ui_pref_security
Since a user has already logged in to the remote server, therefore, I expect WinSCP not to ask the authentication again while doing file modification. If not possible for some reason, then, for the ease of users, WinSCP should use the already stored password and only ask for the token to be entered.
And what is the expected behavior? Do you expect no prompt at all (reusing password and token)? Or is the token one-time only, and you expect no password prompt, but you need a token prompt for a new token?