https://ims-na1.adobelogin.com/ims/exchange/jwt/ giving HTTP error 500 Internal Server Error | Community
Skip to main content
yuhuisg
Community Advisor
yuhuisgCommunity Advisor
Community Advisor
August 2, 2022
Solved

https://ims-na1.adobelogin.com/ims/exchange/jwt/ giving HTTP error 500 Internal Server Error

  • August 2, 2022
  • 1 reply
  • 3471 views

I've been trying the whole day (2 August 2022) to exchange my JWT token at https://ims-na1.adobelogin.com/ims/exchange/jwt/, but keep getting HTTP 500 Internal Server Error. I've faced this problem with 2 different projects, both of which have valid client IDs and secrets. I even generated new JWT tokens with my private key, but still kept getting back the error.

Yet, I don't see any issues/problems at https://status.adobe.com/products/1675.

Is anyone else facing this 500 Internal Server Error problem when exchanging JWT tokens? If it's indeed a problem at Adobe's end, how long will it take to be resolved?

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 miChou

Thanks for looking into this, @tmj 

I am using the web version of Postman in Firefox on macOS, if that makes any difference.

Here are 2 debug IDs: 41803aae-1756-41cf-be32-706667bd42ad, cbb2db24-56a8-41b9-8c49-9edde26faf83

My Postman setup:


I'm pretty sure that cURL is *not* sending the request body as multipart/form-data.

The correct content type is  application/x-www-form-urlencoded.

1 reply

yuhuisg
Community Advisor
yuhuisgCommunity AdvisorAuthor
Community Advisor
August 5, 2022

Strangely, this worked properly with cURL. So now, I'm able to exchange my JWT for the bearer token properly, but only in cURL, not in Postman.

tmj
Adobe Employee
tmjAdobe Employee
Adobe Employee
August 5, 2022

Hi @yuhuisg it is strange that the cURL request works but not through Postman. Maybe it was a temporary glitch as you are able to generate the access token now. 

 

However, if you are still seeing the same behavior, please add the x-debug-id response header to the thread so we can investigate.

 

Thanks,
Manik

tmj
Adobe Employee
tmjAdobe Employee
Adobe Employee
August 11, 2022

@michou , thanks. I can confirm that using "application/x-www-form-urlencoded" gave me the expected successful response.

Looks like the Adobe doc that I was referring to is outdated, then.


@yuhuisg if you could point me to the documentation you are referring to, I can get it fixed. 

Terms & ConditionsAccessibility statement

Loading footer...