OAuth Authentication
Omada Identity accepts OAuth 2.0 access tokens as bearer tokens in the HTTPS Authorization header. This is how applications, scripts, and integrations call the Omada Identity application programming interfaces (APIs) without a user signing in.
The client obtains an access token from your identity provider (IdP) with the client credentials flow and sends it with each request. Omada Identity validates the token and maps it to an Omada Identity user based on the token claims. The request runs with that user’s permissions.
Bearer tokens are accepted when Omada Identity uses OpenID Connect for authentication. For interactive sign-in setup, see Configure Microsoft Entra ID with OpenID Connect or Configure Okta with OpenID Connect.
For the complete setup of an API client in Microsoft Entra ID or Okta, including the service user in Omada Identity, see Authenticate API clients with OAuth.