Can you please expand on this use case? Client credentials are typically seen as user-less tokens. Adding them to an organization and delegating them to a user sounds like you want a user’s token. What would be the difference there?
So I basically just want a token with and org_id parameter generated using the client credentials flow - not sure if this is possible? Of course, as standard with this flow, the client requesting these tokens would be trusted.
I guess this is a two-parter: it would be great to be able to delegate the ability to delegate the ability to do this for a member of an organization for the organization they are in.
Hi @mattbrown1 - thanks for clarifying. This is not currently possible but we are planning to integrate Organizations & client_credentials in a way similar to what you are describing. It would be helpful to understand your use-case a bit more: what does an organization represent in your product? What are these clients requesting access to?
Hi all, I would also be interested in this feature, essentially the ability to add api-keys to an organization, so that their organization ID would appear in the jwt.
Client’s Credential Flow support for Organization is right now in the private Early Access, which you can join by contacting your Auth0 account manager. If you can wait, the General Access for this feature is expected to launch during the second half of this year. I will keep you informed when I will have more information regarding this feature.