Forum Discussion
How to access Dynamics CRM API from PowerBi using Client Id , Client secret and tenant Id using
- 1 year ago
You can validate tokens at jwt.io
- 1 year ago
As from our previous conversation, to verify the access token, you can use jwt.io. When you authenticate using the service principal, you should receive an access token. Go to jwt.io and paste your access token into the "Encoded" field. The tool will decode the token and display its contents. Look for the "scp" section in the decoded token to ensure it includes the necessary permissions to access the Dynamics CRM API. Generating a login bearer token first and then using that token in your API calls can help resolve the issue by ensuring you have a valid token with the required permissions.
Probably you can generate and login bearer token first and then using that token in your API calls can help resolve the issue. This approach ensures that you have a valid token with the required permissions to access the Dynamics CRM API. By including the bearer token in the Authorization header of your API calls, the API can verify that you have the necessary permissions to access the data.
If this post clears your doubt, please give us Kudos and consider marking Accepting it as a solution to guide other members in finding it more easily.
Yes that gave me the client id and client secret and when I query data tables using dataverse for the same environment of dynamics crm using the service principal authentication it works only for the API it didn't work
check the access token ( at jwt.io ) - most likely the "scp" (scope) section is missing or incomplete.
- Harineeeeeeee1 year agoHelper I
@when you refer to use correct authentication method, I am using service principal to authenticate but how to verify the access token? Where can I find that??could you please elaborate
Also I was suggested to generate login bearer token first and then providing that token as part of the api calls, will that help to resolve this issue?
- lbendlin1 year agoSuper User
You can validate tokens at jwt.io