Set Up an OIDC Provider
Create an OIDC app, save the Built LMS provider, and copy callback URLs into the IdP.
Use this guide to create the provider connection between Built LMS and an OIDC identity provider such as JumpCloud, Okta, Microsoft Entra ID, Google Workspace, Auth0, Ping, or another OIDC-compatible provider.
Before you begin
You need:
- Built LMS admin access to Settings > Identity & Access > Authentication.
- Permission to add or edit authentication providers.
- Admin access in the identity provider.
- Permission to create an OIDC application or client.
- The IdP issuer URL.
- A client ID.
- A client secret for the current Built LMS OIDC setup.
Keep a non-SSO admin recovery path available while you configure the provider.
Create the provider connection
Create the OIDC app in the IdP
In the IdP, create an application for Built LMS.
Use an application type that supports the Authorization Code flow, usually one of:
- Web application.
- Confidential client.
- Server-side application.
Configure the app for:
| IdP setting | Recommended value |
|---|---|
| Flow / grant type | Authorization Code |
| Client authentication | Client secret |
| PKCE | Allowed or required when available |
| Redirect URI | Temporary first, then Built LMS final redirect URI after save |
| Scopes | openid, profile, email |
| Claims | email, name, given_name, family_name |
| App assignment | Pilot user or pilot group |
If your IdP will not create a client until a redirect URI is entered, use a temporary value that you will replace after Built LMS generates the final provider URL.
Create the OIDC provider in Built LMS
- Open Admin Dashboard.
- Go to Settings > Identity & Access > Authentication.
- Open Auth Providers.
- Select Add Provider.
- Set Provider Type to OpenID Connect.
- Select Continue.
- On New OIDC Provider, enter a Display Name.
- Enter the Issuer URL, Client ID, and Client Secret from the IdP.
- Select Save Provider.
The page title is New OIDC Provider. The provider is created disabled by default so you can configure and test it before rollout.
Copy callback URLs to the IdP
After the provider has been saved, reopen or stay on the provider edit page and find Copy to Your IdP.
- Copy Redirect URI.
- Paste it into the IdP app's sign-in redirect, authorized redirect, or callback URL field.
- Copy Post-Logout Redirect URL if the IdP supports sign-out redirects.
- Copy Login URL if the IdP supports app tile login, sign-on, or home URL fields.
- Save the IdP app.
The redirect URI must match exactly. Do not use the placeholder text from the new-provider form.
Configure advanced connection options
Most OIDC providers work with the defaults:
- Token Endpoint Auth Method: Client Secret POST.
- Scopes:
openid,profile,email. - Response Type: Authorization Code.
- Endpoint Overrides: blank.
Use Configure OIDC Connection Options when your IdP requires a different token auth method, extra authorization parameters, or manual endpoint overrides.
Verify success
The provider connection is ready for claim mapping and pilot testing when:
- The OIDC provider saves successfully.
- The final Redirect URI has been copied from Built LMS into the IdP app.
- The IdP app uses Authorization Code flow.
- The IdP app requests or allows
openid,profile, andemail. - The provider is still not default while setup is incomplete.
Troubleshooting
Open the discovery document in a browser:
{issuer}/.well-known/openid-configurationIf it does not load, check the issuer URL or use Endpoint Overrides with exact values from the IdP.
Check Client ID, Client Secret, Token Endpoint Auth Method, token endpoint override if used, and whether the IdP client is allowed to use Authorization Code flow.
Copy Redirect URI from the saved Built LMS provider and paste it into the IdP exactly. Common causes include using the placeholder URL, using the wrong domain, leaving an old staging callback, or changing a trailing slash.