SAML 2.0 Identity Provider (SSO) Integration

SAML 2.0 Identity Provider (SSO) Integration

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:

  • One sign-in: People use the login they already have for work, so there is no extra password to remember.
  • Central access control: Your identity provider decides who can reach Auzmor Learn.
  • Works with your provider: Connect Okta, Azure Active Directory, G-Suite, or any other SAML 2.0 compliant provider.

What you need

  • Primary Admin access to Auzmor Learn.
  • Admin access to your identity provider.
  • The ACS URL and Entity ID from Auzmor Learn. You copy these in the steps below.
  • A metadata XML file from your identity provider.

Step by step: set up SSO

  1. Click your profile picture in the top-right corner and select Settings.
  2. Under Organization Settings, click Single Sign-on.
  3. Find your provider and click Configure. Okta, Azure Active Directory, and G-Suite have their own tiles. For any other SAML 2.0 provider, use the SAML tile.
  4. Under Details necessary to create your SAML application, copy the ACS URL and Entity ID. Copy the RelayState/Start URL too if your provider asks for it.
  5. In your identity provider, create a custom SAML 2.0 application and paste in those values.
  6. Send each person's email address as the Name ID. Add first name and last name attributes.
  7. Assign the application to the people who should use Auzmor Learn.
  8. Download the metadata XML file from your identity provider.
  9. Back in Auzmor Learn, under Add metadata XML file, click Upload metadata xml and select the file.
  10. Choose your sign-in options (see the table below).
  11. Click Activate.

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.

Profile picture menu with Settings and Switch to Learner's View

SSO page in Settings with the Active Directory, Azure Active Directory, Okta, G Suite, and SAML tiles

SAML (SSO) tab with ACS URL, Entity ID, and RelayState or Start URL under Details necessary to create your SAML application

Sign-in options

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.

Add metadata XML file with Upload metadata xml and the two sign-in options

How people sign in

  • From Auzmor Learn: On your Auzmor Learn sign-in page, click Sign in with SSO.
  • From your identity provider: Open the Auzmor Learn application from your provider's app dashboard.

Provision users automatically with SCIM

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.

SCIM tab with the Enable SCIM checkbox and the Generate Key button

Common questions

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.

Related articles