Error "JWT has no valid metascope claims" getting access token from IMS using service credentials | Community
Skip to main content
P
pa-c-jekeyser
February 25, 2022
Solved

Error "JWT has no valid metascope claims" getting access token from IMS using service credentials

  • February 25, 2022
  • 1 reply
  • 1223 views

Hello, all.

I have received service credentials for our AEM Cloud service using the process described at https://experienceleague.adobe.com/docs/experience-manager-learn/getting-started-with-aem-headless/authentication/service-credentials.html. At one time, I was able to obtain an access token from our .NET application successfully using custom code to integrate with IMS. However, I am now receiving a 400 "bad request" error when trying to do this now. The error in the response is "JWT has no valid metascope claims." The credentials I received contained the metascope "ent_aem_cloud_api," and that still appears in the credentials when I view them now from the Developer Console. I am translating this into the claim "https://ims-na1.adobelogin.com/s/ent_aem_cloud_api" with a value of "true" before creating the encoded JWT token.

Does anyone have an idea of what might be causing this error?

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 pa-c-jekeyser

This must have been a problem with IMS itself, not our code. We noticed that this it working as of today.

1 reply

P
pa-c-jekeyserAuthorAccepted solution
March 4, 2022

This must have been a problem with IMS itself, not our code. We noticed that this it working as of today.

    Terms & ConditionsAccessibility statement

    Loading footer...