Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

README needs to explain Machine to Machine Applications authorization

Open
#610 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
1/5
Estimated time
Under an hour
Newbie friendliness
50/100
Issue type
Documentation
Clarity
Clearly specified
Activity status
Stale
Tech stack
ruby
Domain
authorization

Research direction

Update the README section that mentions authorizing an application for the Management API. Start by reading the existing authorization guidance and compare it with the issue's described Machine to Machine Applications path. Done means the README explains where to authorize the application and helps prevent the reported access_denied error.

Written by the indexing model from the issue text.

Description

bug
Checklist
  • I have looked into the Readme and Examples, and have not found a suitable solution or answer.
  • I have looked into the API documentation and have not found a suitable solution or answer.
  • I have searched the issues and have not found a suitable solution or answer.
  • I have searched the Auth0 Community forums and have not found a suitable solution or answer.
  • I agree to the terms within the Auth0 Code of Conduct.
Description

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)

This was my implementation of the client:

client = Auth0Client.new(
  client_id: Rails.application.credentials.auth_zero.client_id,
  client_secret: Rails.application.credentials.auth_zero.secret,
  domain: Rails.application.credentials.auth_zero.domain,
)

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
  1. Configure the grant for the application
  2. Create the Ruby client
  3. [Failure]
Additional context

No response

ruby-auth0 version

5.17.0

Ruby version

3.2.2

Dominant language
Ruby
Stars
205
Forks
148
Avg merge
13h
Merged PRs (30d)
4

Getting set up

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from auth0/ruby-auth0

All issues in auth0/ruby-auth0

Similar issues

More Ruby issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.