Invalidate session.properties if config file is updated

[cwarden]

getSavedConnectionData shouldn't return the cached sessionId and serviceEndpoint from session.properties if the config file is newer than the session.properties. When the config file is updated, it should invalidate the session info, and a new session should be started using the current config file.

[neowit]

Hi Christian,

I am guessing that you use config file only for login credentials?
tooling-force.com config file does not have to be limited to login credentials only and can contain any other parameters. Also, login credentials can be passed directly via command line, without a config file.

Perhaps a better option would be to hash login/pass/url combination and store it in session.properties. This way tooling-force.com could check the hash every time it tries to re-use existing session Id to see if that Id is still valid relatively current login attributes.

What do you think?

[cwarden]

I had only been using it for credentials and login url, which is why I suggested using modification date. Hashing the credentials and url, whether from the config file or command line arguments, sounds like an even better solution.

[neowit]

check v0.1.4.3 to see if it works for your use case.

[cwarden]

You had me scratching my head thinking 9b507e9 was the only change you made.

cac400b...9b507e9 indeed fixes the problem. Thanks!