Getting the error "Error in Getting Access Token" while integrating CQ5 with Salesforce | Community
Skip to main content
M
MRG
October 16, 2015
Solved

Getting the error "Error in Getting Access Token" while integrating CQ5 with Salesforce

  • October 16, 2015
  • 4 replies
  • 2811 views

I followed the steps as per the article "Integrating with Salesforce" to integrate CQ5 with salesforce, but I am getting the error "Error in Getting Access Token".

"maruthid" also faced this issue and raised his question in "Integrating CQ and salesforce and possible options" on December 30, 2013, but didn't get any response.

Please help me if someone knows a solution for this. Your help would be greatly appreciated.

    This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.
    Best answer by

    I was not getting the same error as you, but I checked my settings for a test app I had created, and found that I would get an "invalid_grant" error in Cloud Services configuration with some OAuth Scope configurations set for my test app.

     

    One of these two configurations seemed to be required for it to work and connect properly into AEM (or into anything else).

    [img]api-access.png[/img]

    [img]full-access.png[/img]

     

    You can certainly select more (even all) of the available OAuth Scopes, and it should continue to work (it did for me).

     

    Let us know if that works for you. Assuming it does, we can get the documentation updated to be more clear about what minimum OAuth Scopes are required.

    4 replies

    A
    Anonymous
    Accepted solution
    October 16, 2015

    I was not getting the same error as you, but I checked my settings for a test app I had created, and found that I would get an "invalid_grant" error in Cloud Services configuration with some OAuth Scope configurations set for my test app.

     

    One of these two configurations seemed to be required for it to work and connect properly into AEM (or into anything else).

    [img]api-access.png[/img]

    [img]full-access.png[/img]

     

    You can certainly select more (even all) of the available OAuth Scopes, and it should continue to work (it did for me).

     

    Let us know if that works for you. Assuming it does, we can get the documentation updated to be more clear about what minimum OAuth Scopes are required.

      V
      vdhim23
      October 16, 2015

      Have you added the instanceUrl in the configuration node. Also OAuth scope should include refresh_token in your SF App.

      Regards

      M
      MRGAuthor
      October 16, 2015

      Thanks for your response. I tried the configurations as you suggested but no luck. Getting the same error.

      Chandra_gupta
      Chandra_gupta
      July 18, 2016

      HI,

      I have IP relaxation and selected all scope in Connected APP. but still getting Invalid_token error

      {"error":"invalid_grant","error_description":"expired authorization code"}

      You got working with Any AEM version?

      Terms & ConditionsAccessibility statement

      Loading footer...