Hey,
Were you using the AEM cloud and have you implemented this on AEM servlet?
because with servlet, I am getting 400, when trying to hit the exchange token URL and it's working fine in localhost.
Hi Team,
I got an error while trying to connect to the exchange token URL internally via servlet.
"Server returned HTTP response code: 400 for URL: https://ims-na1.adobelogin.com/ims/exchange/jwt"
So basically I am first generating the JWT token using the privatekey.pem file and then hitting t...
@aanchal-sikka
It was /clientheaders where I had to allow the custom header. but then I got another error while trying to connect to the exchange token URL internally via servlet.
"Server returned HTTP response code: 400 for URL: https://ims-na1.adobelogin.com/ims/exchange/jwt"
So basically I a...
Hey Community,
Hope you're doing well.
I'm facing an issue with reading headers such as clientId, clientSecret, and orgId in the AEM cloud publish URL and domain URL via POSTMAN. I have a servlet where I'm reading all these headers, and it's working fine on localhost but not in DEV.
Has anyone encou...
If you don't have any specific parameter requirement, you can go ahead with out-of-the-box graphql implementation with content fragments.
https://experienceleague.adobe.com/docs/experience-manager-cloud-service/content/headless/graphql-api/content-fragments.html?lang=en
It's an error of some dependent jars in a graphql-java.If you'll try to setup the same and use the example Java code provided in the link. you'll see the error during the build.