Enabling Single Sign-On
This guide walks you through how to configure Single Sign-On (SSO) using OpenID Connect (OIDC) for your organization’s end users to securely access the CLEAR Console. CLEAR supports direct integrations with leading identity providers including Okta, Entra (Azure AD), and Ping Identity as well as a standard OAuth/OIDC based SSO.
Prerequisites
Before you begin, ensure the following:
- You have admin access to your CLEAR Console organization. To gain access to the CLEAR Console, please contact [email protected].
- You have admin access to your Identity Provider (IdP).
Setting up SSO for your organization
The CLEAR Console exclusively supports the OpenID Connect (OIDC) protocol for SSO. This ensures secure, standards-based login flows and supports user identity claims such as email and name.
Required OIDC Fields:
- Client ID
- Client Secret
- Discovery URL (well-known configuration URL)**
Step-by-Step Setup
Step 1: In CLEAR Console
- Navigate to the CLEAR Console and select User Management in the left navigation menu.
- Go to the ‘Single Sign-On (SSO)’ tab at the top of the User Management page.
- Select your identity provider: Entra, Okta, or Ping. For any other OIDC based providers, Select ‘Other OIDC’.
- Enter the required OIDC fields that can be found in your respective SSO provider’s admin area:
- Client ID
- Client Secret
- OIDC Discovery Endpoint
- After you’ve entered all three items above, click the ‘Get URI endpoints’.
- If successful, the following fields will automatically populate:
- authorization_endpoint
- token_endpoint
- userinfo_endpoint
- The Redirect URI will be provided on this page. Copy it for your IdP configuration.
- Click Save
Step 2: Configure Your Identity Provider
→ Okta
- In Okta Admin Console, go to Applications > Create App Integration
- Choose OIDC - Web Application
- Fill in application details
- Add the Redirect URI from the CLEAR Console
- Set Grant Type to Authorization Code
- Assign users or groups to the app
- Copy the Client ID, Client Secret, and Okta Domain for the Discovery URL:
https://<your-okta-domain>/oauth2/default/.well-known/openid-configuration
- In Azure Portal, go to App registrations > New registration
- Enter app name and Redirect URI (web)
- After creation, go to Certificates & secrets to generate a new client secret
- Copy the Application (client) ID and Directory (tenant) ID
- Discovery URL format:
https://login.microsoftonline.com/<tenant-id>/v2.0/.well-known/openid-configuration
- Log in to PingOne Admin Console
- Go to Applications > Add Application
- Choose OIDC Web App and provide Redirect URI
- Configure required scopes and attributes
- Retrieve Client ID, Client Secret, and Discovery URI. Your Discovery URI will be in this format:
https://auth.pingone.com/<environment_id>/.well-known/openid-configuration
Step 3: Testing Your Configuration
After saving your IdP configuration in the CLEAR Console:
- Click Get URI Endpoints
- The URI Endpoints should populate below
- Ensure claims (email, name) are correctly mapped
Troubleshooting
| Issue | Solution |
|---|---|
| Invalid redirect URI | Ensure the URI matches exactly in both IdP and CLEAR Console |
| Missing claims | Confirm email and name are included in your IdP’s claim configuration |
| Login fails silently | Verify client secret is correct and has not expired |
| Token expiration errors | Check clock sync on IdP and CLEAR systems |
Updated 25 days ago
Did this page help you?