Omada Identity

Record your Omada Identity connection as user access review evidence. Automated collection is not available for this provider yet.

Connect with an API token

1. In Omada Identity:

   1. In the Microsoft Azure portal, open App Registration and create a new App Registration for API access (the OAuth app).
   2. Edit its Manifest to set "accessTokenAcceptedVersion": 2.
   3. Under Certificates & secrets, select New Client secret and copy the secret immediately; it is displayed only once. Note the Application (client) ID and the OAuth 2.0 token endpoint.
   4. On the Omada OpenID app registration, click Add an Application ID URI, click Set and enter API://[id of the OData AppRegistration]; add an application role there and add the matching API permissions to the OAuth app.
   5. In Omada Identity, create a new User whose Username equals the OAuth app's client ID, and add only the Group memberships that allow read access to OData.
   6. Request a bearer token from the OAuth 2.0 token endpoint with the client credentials and paste it into Safeguard (or record the client ID and secret).

   Omada Identity shows the secret only once, so copy it before you leave the page.

   Omada Identity's public documentation does not cover every step.

   Source is Omada Identity's OAuth guide for version 14.0.16, which uses a Microsoft Entra ID (Azure) app registration; Omada Identity Cloud may differ. The guide does not name the Omada group that grants OData read access, the menu path for creating the user in Omada, or an example OData base URL, so Base URL and Account fields are not documented. Bearer tokens from Entra expire, so the client ID and secret are the durable credential. The Graph API applies the same authentication level rules as the standard Omada session model.

   Source: documentation.omadaidentity.com, documentation.omadaidentity.com, checked 2026-10-07.

2. On Compliance › Connectors, open Omada Identity, click Connect, choose API token and fill in:

   Field	What to enter
   API token / Personal access token	Required. Stored encrypted and never shown again.
   Base URL (optional)	—
   Account / Org / Workspace (optional)	—

3. Click Connect with token.

Frameworks

No automated compliance test reads Omada Identity yet, so no framework lists it. How connectors provide evidence for frameworks: Frameworks and connectors.

Related

• User Access Review connectors
• Compliance connectors: how connecting works, card statuses and multiple accounts
• Connector setup reference: every connector in one table
• Frameworks and connectors: how connectors provide evidence for frameworks