JWT | Community
Skip to main content
M
mmbb110
Level 9
May 8, 2021
Question

JWT

  • May 8, 2021
  • 1 reply
  • 1441 views

I am trying to generate a access token using curl command generated via adobe io console.

 

https://www.adobe.io/authentication/auth-methods.html#!AdobeDocs/adobeio-auth/master/AuthenticationOverview/ServiceAccountIntegration.md

 

I generate the custom JWT and copy the sample curl command from the adobe io console, import that to my postman as shown in the above link and hit send, I get a 500 internal server error.

 

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

 

I am not sure what is wrong, I can generate an access token from the Generate access token option, by using my private key.

 

Open your private key. Then, copy and paste the key in the field. A JSON Web Token (JWT) will be generated and exchanged for your first access token

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

1 reply

SatheeskannaK
Community Advisor
SatheeskannaKCommunity Advisor
Community Advisor
May 11, 2021

Hi @mmbb110,

 

Can you try follow steps outlined here and see if that helps.

https://medium.com/@prajwalshetty_17572/making-api-calls-on-adobe-i-o-adobe-campaign-standard-a7eb85370438

 

Thanks, SK

Thanks, Sathees
M
mmbb110Author
Level 9
May 13, 2021
@satheeskannak, Thank you for the response, I checked that link and it refers to open SSL for generation for public/private key pair, I do not want to use that method and would rather utilize adobe io console where I have already created a project and configured it to generate the private key, also with that same private key, I can generate a bearer token, but when I use the Generate JWT option and paste my private key and then copy the sample curl command and use postman where I import and paste the raw text, after hitting send, I get 500 internal server error, I am not sure why, is the JWT generate not working via adobe io console to get a access token?
Terms & ConditionsAccessibility statement

Loading footer...