Roles: Primary Admin
Description: In this article, you will learn how to connect Auzmor Learn to a SAML 2.0 identity provider. People can then sign in with their company credentials.
Benefits:
Note: Steps 5 to 8 look different in each identity provider. For exact screens, see the Okta, Azure Active Directory, and G-Suite articles listed under Related articles.
| Option | What it does |
|---|---|
| Allow Auzmor Learn to authenticate as a fallback mechanism | Lets people sign in with their Auzmor Learn email and password when your identity provider is down. When this is off, people can sign in only with SSO. |
| Allow only existing users to do SSO | Stops SSO from creating new accounts. Only people who already have an Auzmor Learn account can sign in. When this is off, SSO creates an account the first time someone signs in. |
The SCIM tab in the same dialog lets Okta or Azure Active Directory create and update users in Auzmor Learn for you. Select Enable SCIM and click Generate Key to create your Tenant URL and secret key. Then follow the SCIM article for your provider.
Can I connect more than one identity provider?
No. Auzmor Learn uses one metadata file for your organization, and a new upload replaces the old one. To move to a different provider, contact Auzmor Support so the switch is completed correctly.
What happens to password sign-in once SSO is on?
If the fallback option is off, people can sign in only with SSO. Password sign-in, Forgot Password, and password resets by admins are not available.
Why did SSO create a second account for someone?
Auzmor Learn matches people by email address. If your identity provider sends a different email than the one on the person's Auzmor Learn profile, a new account is created. Make sure your provider sends the work email address.
I use branches. Do I set up SSO once?
No. SSO applies to the organization where you set it up. Set it up in each branch whose people sign in with SSO.