function readOnly(count){ }
Sign Up ›
Starting November 20, the site will be set to read-only. On December 4, 2023,
forum discussions will move to the Trailblazer Community.
Learn More

Browse by Topic
ShowAll Questionssorted byDate Posted
+ Start a Discussion
VladMoushkovVladMoushkov 

INVALID_LOGIN: Invalid username, password, security token; or user locked out for Dev Org

Hello.

We are unable to authenticate with the SFDC API despite entering the correct username, password and security token. The message returned is:

INVALID_LOGIN: Invalid username, password, security token; or user locked out

This is for a developer account, so we are using the https://na15.salesforce.com/services/Soap/u/19.0 API URL. We have also tried with https://login.salesforce.com/services/Soap/u/19.0 and get the same result.

We have tried with an Administrator account and another API enabled account.

However, we know that the username, password and token are all correct. And we can log into the account through the UI front end, so it does not appear to be locked out.

Can anyone advise what we can try next to authenticate please?!

Many thanks,
Jon
Best Answer chosen by VladMoushkov
VladMoushkovVladMoushkov
Hi there,
Supricingly after another attempt yesterday it runs now ok. The only change we did is another password reset.

All Answers

pconpcon
Are you stilll facing this issue?  Are you using the password + token as you password?  Have you tried resetting the token again and ensuring that you have the correct token for the production user?
VladMoushkovVladMoushkov
Hi there,
Supricingly after another attempt yesterday it runs now ok. The only change we did is another password reset.

This was selected as the best answer
pconpcon
Great!  It happens some times.  Most of the time (at least for me), it's human error.  I store the token down wrong, or use the token from a pre-production org.  If you don't mind marking this question as solved, so that it will be removed from the "unsolved" view.
VladMoushkovVladMoushkov
I will do that although I am pretty sure it was not a human error as we tried more than couple of times.
Anne Clisham 7Anne Clisham 7
We had something similar happen as decribed above.  We changed the password and then logged in again with the new password and token but still got an error.  We tested the password change to a sandbox. https://cs22.salesforce.com/services/Soap/u/19.0  Any suggestions? None of our existing connections that we have been using for sometime now are working.