Omada Identity
The Omada Identity connector is a built-in connectivity that enables Omada Identity to govern and provision access within the platform.
Supported objects and operations
N/A
Minimum required permissions
N/A
Implementation notes
For Omada Identity Cloud deployments, the Omada Identity connector is automatically configured during environment setup. No manual connection or additional setup details are required.
For Omada Identity (on-premises) deployments, connection details are not configured automatically. Configure the connection details manually in the system onboarding view. The following authentication methods are supported:
| Authentication Type | Description |
|---|---|
| Integrated (Windows) Authentication | Uses IIS Windows Authentication (Kerberos/NTLM) against Active Directory. Common for internal corporate access. |
| Forms Authentication | Users authenticate with username/password through the Omada login page. |
| SAML 2.0 | Enterprise Server can act as a Service Provider (SP) and delegate authentication to an external Identity Provider (IdP) such as Microsoft EntraID, Okta, PingFederate, ForgeRock, or ADFS. |
| OpenID Connect (OIDC) | Enterprise Server supports OpenID Connect-based SSO with external IdPs including Microsoft Entra ID and Okta. Authentication is delegated to the IdP and ES consumes the returned JWT tokens. |
| Anonymous Authentication | Used during certain installation/setup scenarios and for specific IIS configurations. Not normally used as the end-user authentication model. |
Network requirements
The following URL must be allowed on port 443:
| URL | Protocol | Port |
|---|---|---|
*.omadaidentity.com | HTTPS | 443 |
Prerequisites
N/A