Unable to verify credentials with Salesforce

[Luke Miller]

I regularly run into a problem where I can no longer verify my credentials with Salesforce. When I open the connections setup dialog and click test, I get no result or error referring to this test until I click "OK" in the main dialog.

Then I receive the error "The connection credentials must be successfully verified" and I cannot save. When I check my login history in Salesforce, I see that the credentials did, in fact, result in a successful login.

If I go to deploy metadata and select my production environment, I get an error about an incorrect username, password, security token or user is locked out. I've checked in Salesforce and it still reports a successful login. I've tried creating a new connection and get the same issues.

Last time I ran into this, I had to completely delete IntelliJ and my project and start from scratch.

[Scott Wells]

Sorry that you're hitting this, Luke, especially if it's happening with any regularity. The next time it happens, please attach or email a log file so I can see the stack trace(s) and hopefully help resolve the issue for you.

[Luke Miller]

By checking out the log file I was able to determine I was getting a "Password Expired" error back from my production environment. So I reset the password and updated it in my IlluminatedCloud settings and was able to log in. Seems like the "Password Expired" response from Salesforce doesn't throw an error in the UI for IlluminatedCloud?

One quick note, it looks like every time you test login credentials it runs three login attempts. When troubleshooting issues like these, three attempts seems a bit excessive as within two test attempts I was locked out of one of my sandboxes for exceeding the limit. Not sure if this can be brought down to one attempt per test, just something that cropped up.

[Scott Wells]

Good to know and I'll definitely take a look. I think the real solution is just short-circuiting when the login response comes back with password expired. Otherwise those other two "login" attempts would no-ops because the first login would have succeeded (they're basically doing a loginIfNecessary(), but the lack of short-circuiting is causing multiple failed logins). Thanks for providing the details!

[Luke Miller]

No problem! Thank you for being so responsive!

[Scott Wells]

Issue tracker grooming. If this is still an issue, please feel free to reopen, ideally with a concrete reproduction scenario.