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

Question

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?

miChou · Accepted Answer

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:

Request type: POST
Headers
- Cache-Control: no-cache
- Content-Type: multipart/form-data
Body:
- client_id
- client_secret
- jwt_token
https://ims-na1.adobelogin.com/ims/exchange/jwt/

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.

yuhuisg · Answer

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.

Sign up

Login with SSO

Login to the community

Login with SSO

Scanning file for viruses.

This file cannot be downloaded