Setting Up VergeOS as an Identity Provider with OIDC
Guide on configuring VergeOS as an OpenID Connect (OIDC) identity provider for centralized authentication across multiple systems and tenants.
Overview
This guide walks you through the process of configuring VergeOS as an identity provider using OpenID Connect (OIDC), allowing centralized authentication for multiple VergeOS systems and tenants.
Prerequisites
Administrative access to the VergeOS system
Valid SSL certificate installed on the VergeOS system
Basic understanding of OIDC concepts
URLs of client systems that will use this authentication
Steps to Create an OIDC Application
Access OIDC Settings
Navigate to System > OIDC Applications from the top menu
Click New
Configure Basic Settings
Enter a descriptive Name for the application
Check the Enabled box
Add an optional Description
Set Up Redirect URIs
Enter the callback URL(s) where users will be redirected after authentication
Format:
https://your-system-name.example.comMultiple URIs can be added for different client systems
Using Wildcards
You can use wildcards in redirect URIs:
For multiple systems:
https://examplecorp-site*.example.comFor multiple subdomains:
https://vergesystem.*.example.com
Configure Authentication Options
Force Authorization Source: Optionally select a third-party provider
Map User: Choose if all verified users should map to a specific account
Set Scope Settings (Profile, Email, Groups)
Configure access restrictions if needed
Save Configuration
Click Submit to create the OIDC application
The system will generate a Client ID and Secret
Retrieving Client Credentials
Access Application Dashboard
Navigate to System > OIDC Applications
Double-click your OIDC application
Copy Required Information
Client ID: Copy using the displayed value or copy icon
Client Secret: Use the copy icon (value is hidden)
Well Known Configuration URL: Copy the displayed URL
Best Practices
Create separate OIDC applications for different client groups
Regularly review and update access restrictions
Use specific redirect URIs instead of wildcards when possible
Document which systems are using each OIDC application
Troubleshooting
Common Issues
Authentication Fails
Verify SSL certificate is valid and not expired
Check redirect URI matches exactly
Ensure client ID and secret are correctly copied
Scope Access Denied
Verify required scopes are enabled
Check user permissions in restriction settings
Redirect Problems
Confirm URL format matches redirect URI
Verify wildcard patterns if used
Check for SSL certificate issues
Additional Resources
Feedback
Last updated
Was this helpful?