Insufficient scope but JWT has correct scopes on Node

I double checked the access token, it has scopes. My code is directly from

The Private and Public Routes work as expected but my Scoped Route does not. I have checked the API permissions and they are there. Tried read:test as well as read:message.


Bumping since no ones answered my support ticket.

@weber93 Based on the screenshot, the scope seems to be in the permissions claim and not the scope claim in the access token. The quickstart expects it to be in scope.

Can you change the authorization request which you use to get the access token to include this scope? If you currently use something like "scope": "openid", it should change to "scope": "openid read:messages".

(I just responded to the support ticket as well)

1 Like

This topic was automatically closed 15 days after the last reply. New replies are no longer allowed.