Built LMS Help Center
Settings

Configure OIDC Connection Options

Adjust token authentication, scopes, response type, additional parameters, and endpoint overrides for an OIDC provider.

Use this guide only when your OIDC identity provider needs settings beyond the standard Authorization Code setup.

Before you begin

You need:

  • A saved OIDC provider in Built LMS.
  • Admin access in the identity provider.
  • The IdP's required token authentication method.
  • Any required scopes, authorization parameters, or endpoint URLs from your identity team.

Only add advanced options you can explain and test. Incorrect values can block sign-in for every user who relies on the provider.

Configure protocol options

Configure token authentication

Choose the Token Endpoint Auth Method that matches the IdP app:

Built LMS optionUse when
Client Secret POST (default)The IdP expects the client secret in the token request body.
Client Secret BasicThe IdP expects HTTP Basic authentication at the token endpoint.
None / PKCE onlyOnly when your Built LMS environment supports secretless OIDC and the IdP client is configured for it.

If token exchange fails after the user returns from the IdP, this is one of the first settings to check.

Configure scopes and response type

Built LMS normally uses:

openid
profile
email
ScopeWhy it matters
openidRequired for OpenID Connect.
profileSupplies standard profile claims such as name, given_name, and family_name.
emailSupplies the email claim, which Built LMS requires for profile matching.

To add a scope, type it in Scopes and press Enter. Only add offline_access or other provider-specific scopes if your IdP and security policy require them.

Set Response Type to Authorization Code unless your identity team has a specific reason to use an implicit response type.

Configure provider-specific options

Add additional parameters

Use Additional Parameters for extra query parameters sent to the IdP authorization endpoint.

Examples:

prompt=consent
domain_hint=corp.com
login_hint={{email}}

Incorrect parameters can force unwanted consent screens, send users to the wrong tenant, or block sign-in. Test with a pilot user after saving.

Use endpoint overrides

Leave Endpoint Overrides empty for normal OIDC providers.

Use overrides only when:

  • The issuer discovery document is unavailable.
  • The IdP uses non-standard endpoint paths.
  • Your identity team gives you exact endpoint URLs.

Overrides include:

Built LMS overrideWhat it replaces
Discovery URL{issuer}/.well-known/openid-configuration
Authorization EndpointThe discovered authorization endpoint.
Token EndpointThe discovered token endpoint.
UserInfo EndpointThe discovered UserInfo endpoint.
JWKS URIThe discovered signing key endpoint.

If you use overrides, keep an internal note explaining why. Future SSO troubleshooting is harder when discovery is bypassed.

Verify success

Advanced OIDC settings are correct when:

  • The provider saves without errors.
  • Discovery or endpoint overrides resolve to the intended IdP endpoints.
  • A pilot user can complete sign-in.
  • The email claim is present after sign-in.
  • Token exchange succeeds without changing the callback URL.

Troubleshooting

On this page