When Firing:
To obtain an access token, you now may notice the following error in the response:
‘’ Scopes from metascope are not a subset of the client id scopes ‘’
You must now do the following:
Solved! Go to Solution.
Topics help categorize Community content and increase your ability to discover relevant content.
Views
Replies
Total Likes
You can get the metascope link form the jwt tab in the integration. That should work. If you can share the jwt tab screenshot , I can let you know exact link that need to taken and used in the code for api integration.
Views
Replies
Total Likes
@joshua.eisikovits , Thanks for sharing this. Is there any documentation that reflects this change ?
Views
Replies
Total Likes
Added, but still showing the same error.
Views
Replies
Total Likes
jayg26932123 can you provide more details of the error you are getting. what solution you have used to create the JWT integration and have you added the profile so that the integration has required permissions.
Views
Replies
Total Likes
ankits28281247 I am able to fix that JWT Metascope issue and now my microservice is ready . Thanks though for your kind support
Views
Replies
Total Likes
Hi jayg26932123
How were you able to fix the jwt metascope issue? I am getting the same error and I cannot seem to figure out how to fix it. Thank you!
Views
Replies
Total Likes
richardk22096977 can you provide some more details as at what step you are getting the error, is it when you are exchanging the JWT token?
Views
Replies
Total Likes
You can get the metascope link form the jwt tab in the integration. That should work. If you can share the jwt tab screenshot , I can let you know exact link that need to taken and used in the code for api integration.
Views
Replies
Total Likes
Views
Likes
Replies
Views
Likes
Replies