You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When trying to create a client and having the proper grants enabled for my application, I still came across this error:
{"error":"access_denied","error_description":"Client is not authorized to access \"https://dev-x3r4mfeuopyc566w.us.auth0.com/api/v2/\". You need to create a \"client-grant\" associated to this API. See: https://auth0.com/docs/api/v2#!/Client_Grants/post_client_grants"}(Auth0::AccessDenied)
I re-read the README and missed this part: "and that the application is authorized for the Management API". I assumed that enabling the grant did this as well. After doing some research, I came across this issue that explained the need to authorize the application under "Machine to Machine Applications" in APIS.
This should probably be added to the README as:
To authorize your application for the Management API, please visit Applications > APIs > Machine to Machine Applications and then toggle the Authorize button for the application you're integrating with.
Reproduction
Configure the grant for the application
Create the Ruby client
[Failure]
Additional context
No response
ruby-auth0 version
5.17.0
Ruby version
3.2.2
The text was updated successfully, but these errors were encountered:
Checklist
Description
When trying to create a client and having the proper grants enabled for my application, I still came across this error:
This was my implementation of the client:
I re-read the README and missed this part: "and that the application is authorized for the Management API". I assumed that enabling the grant did this as well. After doing some research, I came across this issue that explained the need to authorize the application under "Machine to Machine Applications" in APIS.
This should probably be added to the README as:
Reproduction
Additional context
No response
ruby-auth0 version
5.17.0
Ruby version
3.2.2
The text was updated successfully, but these errors were encountered: