We have many APIs and services, which are accessed by humans and non-human identities (M2M), like ETL jobs, ML training jobs, backend services, dynamically registered mobile devices, which do not act on behalf of a human user. Currently we are using Client Credentials or dynamically create users in…

Hi @Legion2 , Welcome to the Auth0 Community! Thanks for the thorough explanation of your use case. As you have stated, the Oauth2-y way of handling this type of application is to use the client credentials grant. This grant is designed for use with M2M applications, and is meant for the type of no…

Now that three years have passed, does Auth0 support exchanging a workload identity for an M2M access token, or does it still only support the client credentials flow using client IDs and secrets to obtain an M2M access token?

Hi everyone! Even though there is not a solution provided to directly tackle this issue, the Custom Token Exchange feature should be suitable enough to implement in similar scenarios where special credentials must be handled within the Auth0 context. Kind Regards, Nik

How to handle large number of non Human Identities with Auth0

Product Feedback

sdsea April 3, 2026, 9:57pm 4

This may cross over with Support Azure AD Federated Credentials in Enterprise Connections

Topic		Replies	Views
Dealing With Non-Human Identities Blog Discussions authentication , authorization , identity , m2m , ai	1	38	September 9, 2025
Is there a concept of a service account in Auth0 Archived api , mqtt , service-account , system-account	2	8621	December 12, 2017
Single M2M app to give access to API to many users Get Help forum	6	3333	June 13, 2022
Which API to use for federating users with external SP Archived	2	3109	March 28, 2019
More Extensible Machine-to-Machine Flow Product Feedback aws-credentials , machine-to-machine , actions	1	896	September 15, 2023

How to handle large number of non Human Identities with Auth0

Related topics