generating access token using jwt | Community
Skip to main content
sriram_1
Level 3
Jul 18, 2022 6:46 AM UTC
Solved

generating access token using jwt

Hi Team,

I am trying to get access token by Sending 'POST' request to

URL: https://ims-na1.adobelogin.com/ims/exchange/jwt

Post parameters: client_id:...

                             Client_secret:...

                            jwt_token:...

 

 

but getting below error

Response Code: 400
{"error_description":"No valid bindings were found for organization and technical account combination","error":"invalid_token"}

 

could you please help me what could be the reason?

 

Thank you,

Sriram

 

 

 

This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.
Sachin_Arora_
Sachin_Arora_Accepted solution
New Participant
Jul 18, 2022 10:32 AM UTC

Please check following :

  1. Verify the technical account ID value you are passing.
  2. Check if the Integration is made for the correct Organization.
  3. It can also be caused because the public certificate from the integration is expired. Renew the private and public key. Then, upload the public key, and replace the old private key with the new key

You can refer this document which is specific for UST but the error you mentioned is common and above points should be valid in you case as well.

 

https://helpx.adobe.com/in/enterprise/kb/UMAPI-UST.html?#Novalidbindingswerefoundfororganizationandtechnicalaccountcombination

 

View reply

2 replies

SantoshSai
SantoshSai
New Participant
Jul 18, 2022 3:15 PM UTC

Hi @sriram_1 ,

Please check this article if it helps: https://experience-aem.blogspot.com/2021/07/aem-cloud-service-get-adobe-ims-jwt-and-aem-access-token-using-post-man-aem-sso.html

Regards,

Santosh

Translate
Santosh Sai
    Sachin_Arora_
    Sachin_Arora_Accepted solution
    New Participant
    Jul 18, 2022 10:32 AM UTC

    Please check following :

    1. Verify the technical account ID value you are passing.
    2. Check if the Integration is made for the correct Organization.
    3. It can also be caused because the public certificate from the integration is expired. Renew the private and public key. Then, upload the public key, and replace the old private key with the new key

    You can refer this document which is specific for UST but the error you mentioned is common and above points should be valid in you case as well.

     

    https://helpx.adobe.com/in/enterprise/kb/UMAPI-UST.html?#Novalidbindingswerefoundfororganizationandtechnicalaccountcombination

     

    Translate
      Terms & ConditionsAccessibility statement

      Loading footer...