Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Client credentials flow: organisation parameter is ignored #620

Open
5 tasks done
alfechner opened this issue May 18, 2024 · 0 comments
Open
5 tasks done

Client credentials flow: organisation parameter is ignored #620

alfechner opened this issue May 18, 2024 · 0 comments
Labels
bug This points to a verified bug in the code

Comments

@alfechner
Copy link

alfechner commented May 18, 2024

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

The organization parameter of the client_credentials flow is ignored.

From the docstring:

organization (str, optional): Optional Organization name or ID. When included, the access token returned
will include the org_id and org_name claims

However, if I pass the organization id it's ignored and neither org_id nor org_name shows up in the token.

I'm wondering if I need to assign the client app to an organization first but there is no way to do that nor did I find anything related in the docs.

Reproduction

  1. Generate a token using client_credentials flow and pass a valid org id via the organization parameter.
  2. Decrypt the token using e.g. jwt.io.
  3. The claims org_id nor org_name are missing

Additional context

No response

auth0-python version

4.7.1

Python version

3.12

@alfechner alfechner added the bug This points to a verified bug in the code label May 18, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug This points to a verified bug in the code
Projects
None yet
Development

No branches or pull requests

1 participant