remember login working correctly?

[jp1982]

Hello Vault team! I am running client/server version 3.1.9.3798.

the initial steps of my app is setting the remember login ON so all the commands I execute within my application do not require to specify the credentials info and repository. My app is executed from a scheduled task. It works correctly but sometimes I've seen this error: "Please specify -user, -password, and -host"

I check each file that is going to be built to ensure it exists; the example below is the last output I received. Clearly it started to work correctly returning that MyFile and MyFile2 does not exist in the repository (this is because it has a wrong path) but since that point on, for all the rest of the files going in I get the message I mentioned above which makes no sense at all. It started working correctly and then stopped?

CHANGE #1
-> v23 $/MyFile -> MyFile does not exist
-> v4 $/MyFile2 -> MyFile2 does not exist
-> v1 $/MyFile3 -> Please specify -user, -password, and -host.
-> v1 $/MyFile4 -> Please specify -user, -password, and -host.

After receiving this output I executed my scheduled task again and worked with no issues, returning all messages until the last file. Any idea when this occurs? Thanks.

[Beth]

Do you always get a login error whenever there is some other type of error? For example, if you checked on invalid files so that an error was thrown, but don't resolve the issue with the invalid files and run it again, does it always have problems with the login?

If you can capture the failure, you might at the end of capturing the failure have it login again.

[jp1982]

The problem is that it fails one time and the next time runs correctly. My scheduled task just sent the same "Please specify -user, -password, and -host." message (runs @ 2 PM PST) after checking the first 5 files correctly. Not sure why it happens but it is not consistent so I am not sure I will be able to test my code prior releasing it. So it returns these messages 1 time and then if I re-run the task, it does not have the same output which is a little frustrating.

But I am curious why the rememberlogin sometimes fails? You think probably my code makes it forget the credentials at some point? After the remember login, the only 2 commands I run are the setworkingfolder (which runs successfully) and history (which works at the first 3 files and then asks for the credentials). At the end of the app I run unsetworkingfolder and a forgetlogin but these did not get executed.

[Beth]

I'm not sure it should lose the session when an error happens, but that is what it looks like is happening. I'll have to run a test on this, or if you add in an additional login to see what that does.

Do you have any errors in the Vault server log at %windir%\temp\sgvault\sgvault.log that occur at the same time as the login error you receive? Also, check the Event Viewer logs on the server and your client to see if any errors are showing up there at the same time.

Remember login just stores the login information in a file that gets read again every time you perform a command. It's possible that file is being locked when it tries to retrieve the data from it.