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

[pa-c-jekeyser]

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/a.... 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?

[pa-c-jekeyser · Accepted solution]

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