Title: Error 400: invalid client credentials
Last modified: July 3, 2020

---

# Error 400: invalid client credentials

 *  Resolved [James Roberts](https://wordpress.org/support/users/james-roberts/)
 * (@james-roberts)
 * [5 years, 9 months ago](https://wordpress.org/support/topic/error-400-invalid-client-credentials/)
 * Hi.
 * I’m trying to connect/authenticate SalesForce. I’ve followed the steps here [https://github.com/MinnPost/object-sync-for-salesforce/blob/master/docs/initial-setup.md](https://github.com/MinnPost/object-sync-for-salesforce/blob/master/docs/initial-setup.md),
   and when I click the “Connect To SalesForce” button in the Authorize tab in WordPress,
   I then get redirected to SalesForce to login as expected and click “Allow”, but
   when I get re-directed back to WordPress, I see a message reading “Error 400:
   invalid client credentials”. This error is in the same location that the “Connect
   To SalesForce” used to be, before I clicked it and got directed to SalesForce.
 * I think this may have something to do with the “Login Base URL” being set to 
   [https://test.salesforce.com](https://test.salesforce.com) (which is where I 
   logged in when I created the “Connected App” in SalesForce.
 * Any help would be appreciated.
 * Thanks,
    James.

Viewing 3 replies - 1 through 3 (of 3 total)

 *  Plugin Author [Jonathan Stegall](https://wordpress.org/support/users/jonathanstegall/)
 * (@jonathanstegall)
 * [5 years, 9 months ago](https://wordpress.org/support/topic/error-400-invalid-client-credentials/#post-13070001)
 * You might try [this thread](https://wordpress.org/support/topic/cant-authorize-4/)
   where someone had a possibly similar issue.
 * But certainly it is not an issue with using test.salesforce.com. You should always
   use that (for sandboxes) or login.salesforce.com (for production).
 * Other possibilities, from what I can remember:
 * 1. Your other credentials are incorrect (the consumer key or secret)
    2. The 
   Salesforce app hasn’t finished initializing (it takes several minutes for it 
   to do this) 3. Multisite (this plugin may not work in multisite environments)
 *  Thread Starter [James Roberts](https://wordpress.org/support/users/james-roberts/)
 * (@james-roberts)
 * [5 years, 9 months ago](https://wordpress.org/support/topic/error-400-invalid-client-credentials/#post-13070009)
 * Thanks, I have read through that thread, but I’ll go back through it in case 
   I missed anything.
 * 1. I did double check, but I will check again.
    2. I set up about 30 minutes 
   ago, and still experiencing the issue. 3. We are not running a multisite, just
   a normal WP installation.
 * I’ll report back after going through that thread again.
 * Thanks,
    James.
 *  Thread Starter [James Roberts](https://wordpress.org/support/users/james-roberts/)
 * (@james-roberts)
 * [5 years, 9 months ago](https://wordpress.org/support/topic/error-400-invalid-client-credentials/#post-13070040)
 * It’s working now 🙂 I think I just needed to wait longer. Sorry for the inconvenience
   and thanks for the quick reply.

Viewing 3 replies - 1 through 3 (of 3 total)

The topic ‘Error 400: invalid client credentials’ is closed to new replies.

 * ![](https://s.w.org/plugins/geopattern-icon/object-sync-for-salesforce.svg)
 * [Object Sync for Salesforce](https://wordpress.org/plugins/object-sync-for-salesforce/)
 * [Frequently Asked Questions](https://wordpress.org/plugins/object-sync-for-salesforce/#faq)
 * [Support Threads](https://wordpress.org/support/plugin/object-sync-for-salesforce/)
 * [Active Topics](https://wordpress.org/support/plugin/object-sync-for-salesforce/active/)
 * [Unresolved Topics](https://wordpress.org/support/plugin/object-sync-for-salesforce/unresolved/)
 * [Reviews](https://wordpress.org/support/plugin/object-sync-for-salesforce/reviews/)

 * 3 replies
 * 2 participants
 * Last reply from: [James Roberts](https://wordpress.org/support/users/james-roberts/)
 * Last activity: [5 years, 9 months ago](https://wordpress.org/support/topic/error-400-invalid-client-credentials/#post-13070040)
 * Status: resolved