Omega supports SAML 2.0 Single Sign-On, so your users can sign in to Omega through your identity provider (IdP) instead of an Omega username and password. It works with any SAML 2.0 IdP, including Okta, Microsoft, Google Workspace, OneLogin, JumpCloud, Duo, and Auth0.
Overview
Create a SAML application for Omega in your IdP using the details below
Configure the employeeNumber attribute
Set each user's External Integration ID in Omega
Send Omega support your IdP details
Turn on SAML in your Account Settings
Step 1: Create a SAML application in your IdP
Create a new SAML 2.0 application (sometimes called a "custom" or "non-gallery" app) and enter these Service Provider (SP) details. Replace YOUR_OMEGA_ACCOUNT_ID with your Account ID.
Setting | Value | What your IdP may call it |
Assertion Consumer Service (ACS) URL | https://app.omegaedi.com/api/2.0/Authenticate?saml_acs&saml&folder=YOUR_OMEGA_ACCOUNT_ID | Okta: Single sign-on URL |
Recipient / Destination URL | Same as the ACS URL | Okta: Recipient URL, Destination URL |
SP Entity ID | Omega support will provide this | Okta: Audience URI (SP Entity ID) |
Default Relay State | Okta: Default RelayState | |
Name ID format | Unspecified (Omega does not use the Name ID) | Okta: Name ID format |
Note: Use app.omegaedi.com exactly as shown. Do not substitute your Omega subdomain.
Your IdP must allow IdP-initiated sign-on. When a user clicks Sign In on the Omega login page, Omega sends them to your IdP, and your IdP posts a signed SAML response back to the ACS URL.
Step 2: Configure the employeeNumber attribute
Add an attribute statement (Microsoft calls this a claim) named exactly employeeNumber. The name is case-sensitive.
Its value is how Omega identifies the user, so it must be unique for each user and should not change. An employee ID or email address works well.
Microsoft: When you add the claim, leave the Namespace field blank so the claim name is just employeeNumber.
Example: Okta
In Okta, open your app's General tab and click Edit under SAML Settings.
Fill in the fields with the values from Step 1.
Under Attribute Statements, add employeeNumber.
Step 3: Set each user's External Integration ID in Omega
In Omega, edit each user and set the External Integration ID field to the same value your IdP sends in employeeNumber for that person. If the values don't match exactly, the user can't sign in.
Step 4: Send us your IdP details
Contact Omega support with these three values from your IdP:
What we need | What your IdP may call it |
IdP Entity ID | Okta: Identity Provider Issuer |
IdP sign-on URL (the URL Omega sends users to when they click Sign In) | Okta: Identity Provider Single Sign-On URL |
IdP signing certificate (X.509, Base64/PEM) | Okta: X.509 Certificate |
You can also send us your IdP's metadata XML file, which contains the Entity ID and certificate.
Note: If your IdP's signing certificate expires or is rotated, send us the new certificate before it takes effect, or your users won't be able to sign in.
Step 5: Turn on SAML
After we confirm your setup, go to Account Settings, open the Basic tab, set Login Options to SAML 2.0 Single Sign-On, and click Save.
From then on, users can only sign in through your IdP, not with an Omega username and password.
Troubleshooting
"User not found... Contact your administrator": The employeeNumber value your IdP sent doesn't match any user's External Integration ID in Omega. Check the attribute name and the user's value in Omega.
"Not authenticated": Omega couldn't validate the SAML response. Usually the signing certificate or IdP Entity ID we have on file doesn't match your IdP. Contact support.


