I'm running into an issue where I am receiving error messages after starting the authentication flow in my Named Credential and Apex code where my authentication provider didn't receive a refresh token from my external source. I normally generate the refresh token myself with the external source, however I don't see a spot in the SF Auth. Provider or Named Credential settings to store it. How would I keep and utilize my external source's refresh token in SF since the refresh token itself doesn't expire?

Named Credential error message:

The authentication provider didn't provide a refresh token. If the access token expires, your org won't be able to access this named credential.

Apex Raw Log output:

Execute Anonymous: AuthCallout.basicAuthCallout();
10:19:48.1 (1119358)|USER_INFO|[EXTERNAL]|00xx000000xxxxx|user@corporation.com.user|Eastern Standard Time|GMT-04:00
10:19:48.1 (1139619)|EXECUTION_STARTED
10:19:48.1 (1144456)|CODE_UNIT_STARTED|[EXTERNAL]|execute_anonymous_apex
10:19:48.1 (15839897)|METHOD_ENTRY|[1]|000000000000000|AuthCallout.AuthCallout()
10:19:48.1 (15876984)|METHOD_EXIT|[1]|AuthCallout
10:19:48.1 (15909222)|METHOD_ENTRY|[1]|000000000000000|AuthCallout.basicAuthCallout()
10:19:48.1 (257227020)|USER_DEBUG|[12]|DEBUG|{
  "error": {
    "code": "InvalidAuthenticationToken",
    "message": "CompactToken parsing failed with error code: 80049217",
    "innerError": {
      "request-id": "xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxxxx",
      "date": "2018-06-12T14:19:49"
10:19:48.1 (257254508)|METHOD_EXIT|[1]|000000000000000|AuthCallout.basicAuthCallout()
10:19:48.1 (258832440)|CODE_UNIT_FINISHED|execute_anonymous_apex
10:19:48.1 (259654615)|EXECUTION_FINISHED

The funny thing about my Named Credential is that under Authentication Status, it says "Authenticated" after it completes the Authentication Flow on Save. I also don't have the "Generate Authorization Header" box checked.

1 Answer 1


Manually generating a refresh token and putting it in to Salesforce is not supported. You need to check the documentation for your provider; typically, they require a special "scope" in order to provide a refresh token (typically "offline" or "refresh" or something). The refresh token is stored by Salesforce and automatically generates new access tokens on demand automatically during a 401 error.

There's no place to enter such a token because it's supposed to be obtained during the login flow, and is automatically stored securely by the platform. For example, if you were connecting to another Salesforce org, you'd probably use a scope like "api,refresh_token", which would indicate that you're requesting API access and a refresh token.

  • Thanks sfdcfox, that makes a lot more sense and I never knew that. It definitely resolved the error message with the Named Credential, but I'm still getting the InvalidAuthenticationToken errors in the Apex code. I think there may be a missing setHeader in my code somewhere. I have the "Accept" type set to "application/json", but this particular error usually points to a bad JWT token through the third party. Jun 12, 2018 at 15:47
  • @murkywaters You may want to check the "Generate Authorization Header" and see if that fixes things.
    – sfdcfox
    Jun 12, 2018 at 16:05
  • Hmm... doesn't seem to. I do get actual HTML code this time around, but it's an HTTP Error 400 (The request has an invalid header name). I do recall there being something about the third party requiring submissions to pull access and refresh tokens using the request body instead of the request headers. Jun 12, 2018 at 17:16
  • It might be something on my end. By removing all the setHeaders in my Apex class, I'm now getting a "resource not found for my URL segment" message and I think this is something with my third party. Jun 12, 2018 at 17:28

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

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