Authentication
Choose the right authentication task for sign-in providers, login page presentation, provisioning, password rules, and sessions.
Use Settings > Identity & Access > Authentication to control how people sign in, how the sign-in page looks, whether users and groups are provisioned from an identity provider, and how long sessions remain active.
This page is for admins who own account access. Treat changes here as production access changes, not cosmetic edits.
Before you begin
You need:
- Admin access to authentication settings.
- A recovery admin account that can still sign in if an SSO provider is misconfigured.
- Identity provider admin access if you are configuring SAML, OIDC, or SCIM.
- A pilot user account for testing learner and admin access.
- Agreement on whether accounts are managed manually, by SSO, by SCIM, or by an HRIS sync.
Do not disable the only working sign-in method until you have tested the replacement with a non-admin pilot user.
Choose the authentication task you need
Use the focused guide that matches the job:
- Manage Auth Providers to add, enable, disable, or remove email/password, SAML, and OIDC sign-in methods.
- Customize the Login Experience to adjust login copy, branding, provider buttons, and provider order.
- Configure SCIM Provisioning to sync users, groups, and profile attributes from an identity provider.
- Configure Password and Session Security to set password rules, session duration, idle timeout, and reauthentication.
Choose the right access model
Most organizations use one of these models:
| Model | Use it when | Watch out for |
|---|---|---|
| Manual email/password | Small teams, pilots, or organizations without enterprise identity infrastructure. | Admins must manage account creation, password reset expectations, and offboarding. |
| SSO without SCIM | Users should sign in with the identity provider, but account lifecycle is still managed manually or by invitation. | Users may not exist until invited or first provisioned by another process. |
| SSO with SCIM | IT owns account lifecycle and group membership. | Manual changes to synced fields or groups can be overwritten by the source system. |
| HRIS or external sync plus SSO | HR owns people data, IT owns sign-in. | Be clear which system owns profile fields, groups, role assignment, and deactivation. |
If you are not sure which model your organization uses, confirm before editing SCIM mappings or manually changing synced users.
Verify success
Authentication setup is working when:
- The expected provider appears on the sign-in page.
- Disabled providers are hidden or unusable.
- A pilot learner and pilot admin can sign in.
- Roles and permissions match after sign-in.
- SCIM-created users and groups appear as expected when SCIM is enabled.
- Password and session rules do not interrupt critical learner workflows.
Troubleshooting
Use the SAML or OIDC setup guide for provider-specific checks. Common issues are incorrect callback or redirect URL, wrong issuer, missing email claim, invalid certificate, or a provider left disabled after setup.
Open Login Customization and check provider button text, logo, display order, and whether the provider is enabled.
The field is likely owned by SCIM, HRIS, or another external sync. Update the source system or remove the mapping if Built LMS admins should own the field.