How To: Configure Omnigo as an OIDC Client

Version Affected: All
 
 

Overview

Setting up Omnigo to work as an OpenID Connect (OIDC) client against a SecureAuth realm is straightforward. Create and configure an OIDC realm as normal, then supply Omnigo with the realm's Authority URL, Client ID, and Client Secret.

1. Omnigo uses the Authority URL to reach the realm's OIDC metadata, which lives at a fixed subpath of the realm: <Authority URL>.well-known/openid-configuration. Omnigo appends that subpath automatically, so set the Authority URL to just the realm's base URL — for example, if the metadata is at https://idp.example.com/secureauth123/.well-known/openid-configuration, set the Authority URL to https://idp.example.com/secureauth123/.
2. To get the Client ID and Client Secret, open the SecureAuth Admin Console, go to Advanced Settings > Post Auth for the realm, and click the OIDC Client to reveal both values.
   Omnigo's Identity Provider setup form, with the Authority URL, ClientId, and ClientSecret fields filled in (the ClientId, ClientSecret, and Tenant ID values are redacted in this example).

SecureAuth Knowledge Base Articles provide information based on specific use cases and may not apply to all appliances or configurations. Be advised that these instructions could cause harm to the environment if not followed correctly or if they do not apply to the current use case.

Customers are responsible for their own due diligence prior to utilizing this information and agree that SecureAuth is not liable for any issues caused by misconfiguration directly or indirectly related to SecureAuth products.