Salesforce Stack Exchange is a question and answer site for Salesforce administrators, implementation experts, developers and anybody in-between. It's 100% free, no registration required.

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

I recently moved my codebase onto a new development org, and had to switch from "Remote Access" configuration to "Connected Apps" for my OAuth2 Web Services flow.

After getting everything set up, I found that I was no longer getting a refresh token in response to my request. The access_token works, but I assume it will eventually expire.

Is this because my Connected App configuration is still in a "Pending" state? I'm not ready to establish a namespace for development (a requirement for publishing a Connected App, according to this question), and I assume that's why the app is listed as Pending.

share|improve this question
It does appear that you have to commit to a namespace first. But why not just pick one, and if you change your mind later, just spin up a new dev org with the one you really want and migrate everything over to it? Not ideal, but may get you unstuck at least. – Adam Dec 12 '12 at 18:23
up vote 2 down vote accepted

Actually, it might not have anything to do with the namespace.

After configuring a namespace, it still wasn't working. I took a closer look at the "Selected OAuth Scopes" section, and determined that I needed to enable "Perform requests on your behalf at any time" in order to get the refresh token.

share|improve this answer

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.