Integrating Single Sign-On (SSO) with your Tovuti LMS enhances security for your learners while streamlining the sign-in and registration experience. This article provides step-by-step guidance on how to set up SSO and apply it to your login or landing page for a seamless user experience.
This article outlines the following concepts:
- Supported SAML/OAuth Systems
- Add Single Sign-On Option
- User Profile Field Mapping tab
- User Group Mapping tab
- Add SSO to the Login Page
- Include SSO on a Landing Page
Supported SAML/OAuth Systems
Tovuti supports the following SSO systems that are supported by SAML or OAuth2.0.
SAML
-
OneLogin
-
AuthO
-
Centrify Identity Service
-
Microsoft Azure Active Directory (view setup guide)
-
Microsoft Active Directory Federation Services (ADFS) (view setup guide)
-
Okta Identity Management (view setup guide)
-
Idaptive Next-Gen Access
-
Amazon Cognito
-
SecureAuth Identity Platform
-
VMware Workspace One
-
EmpowerID
-
Optimal IdM
-
CloudCodes
-
LastPass Enterprise
-
Ping Identity PingOne
-
Salesforce Identity
-
+ Generic support for SSO systems that use SAML 2.0
OAuth2
-
AWS Cognito (view setup guide)
-
Google Apps
-
Facebook
-
LinkedIn
-
Instagram
-
Windows Account
-
Other OAuth2 supported Identity Providers
Add Single Sign-On Option
Go to Configuration > Click Single Sign-On > Click Add
Details tab
In Details tab, give this option a Title. Select which SSO Type and the Application.
For this SSO Option to be later added to a Landing Page, it must be included in a Navigation Menu. If applicable, add this SSO Option automatically here.
Service Provider Settings tab
In the Service Provider Settings tab, provide the EntityID/Issuer for the SSO provider.
Identity Provider Settings tab
In the Identity Provider Settings tab, provide the SAML information for this SSO option and test the Connection.
Profile Mapping utilizes information that already exists in a user's SSO profile and transfers it to their Tovuti profile (all info is found in the User Manager). This information can be automatically updated when users log in using an SSO integration by setting up the proper attributes and triggers.
User Profile Field Mapping tab
Go to the User Profile Field Mapping tab. The following fields are described below.
The IdP Attribute used while mapping depends on which Single Sign-On Provider is being connected to Tovuti. Some providers utilize a Profile Name system (givenname), while other providers use links (Ex: https://www.sso.com/profile/givenname).
Single Sign-On Provider Attributes
Please refer to the Single Sign-On Provider's specific Customer Service for more detailed information.
1. Name IdP Attribute - the profile attribute in the SSO directory that pulls in the user's Name.
2. Username IdP Attribute - the profile attribute in the SSO directory that pulls in the user's Username.
If fields 1 or 2 are left blank, the user's email is used to generate Name and Username.
3. Email IdP Field - the profile attribute in the SSO directory that pulls in the user's Email.
4. Add another Profile Field - press the green '+' to add additional profile fields that is collected when the user logs in.
5. Choose an additional profile field
Additional profile fields can be created beforehand to be included in this mapping and elsewhere in Tovuti. For information on how to manage and create profile fields, view the Help Center article here.
6. IdP Attribute - the profile attribute in the SSO directory that corresponds to the chosen profile field.
If the corresponding IDs or attributes are not found when logging in, the user's profile field won't include the specific profile field.
User Group Mapping tab
Go to the User Group Mapping tab. Each field will be described below the image.
User Group Mapping Fields
1. Update User Groups on Every Login - designate if a user's User Group information will be updated only the first time they log in or every subsequent login.
It is recommended to disable this toggle while testing and enable it when ready to go live.
2. Default User Group - the primary group this user will belong to.
Default should remain "Registered." "Registered" is a required User Group without which a user can successfully log in.
3. Group Attribute Name - the attribute that maps the user to these groups. Tovuti will search for the Group Attribute Name or ID when the user logs in using SSO.
The group attribute name is found in the SSO's directory.
This attribute above is for groups and not profile fields.
4. Add another User Group - press the green '+' to add additional user groups that users will be added to when they log in.
5. Choose an additional User Group
Utilizing SSO User Group Mapping for User Group Management overrides User Groups assigned in the User Manager. If you plan to use this feature, make sure to include roles such as "Sub-Administrator" and "Site Administrator" in this configuration.
If not included, Tovuti will judge them as "unnecessary" according to the mapping programming, override the User Manager, and a user logging in with SSO will be removed from these groups. This includes admin user groups.
6. IDP Group/Role Identifier - link or role name that maps this group.
If the corresponding IDs or attributes are not found when logging in, the user will not be added to the User Group.
Add SSO to the Login Page
Single-Sign On options can be added to a Login Page to help users log in quickly and with added security.
Login Pages
In the Login Pages editor, view the Details tab.
Select SSO Option
Scroll to the bottom of the page and select an active SSO integration in the Single Sign-On Options field. The selected SSO integration is added to the Login Page.
To require that Users log in via SSO; ensure that Login Form, Include Password Reset, and Include Registration fields are set to No.
Click Save.
User View
From the User Portal, an SSO login option looks like the screenshot below.
Logging in or registering via SSO may utilize some profile information from the SSO directory.
Include SSO on a Landing Page
Landing Pages are often utilized to create a branded experience that highlights content in a logged-out view.
In addition to displaying Courses and Events, the Landing Page can be configured to include a Single Sign-On (SSO) option. This allows learners to quickly register or sign in to the LMS, creating a more efficient and user-friendly access point.
This article outlines the following concepts:
- Include SSO in the Correct Navigation Menu
- Include the Navigation Menu on the Landing Page
- Learner Experience
Include SSO in the Correct Navigation Menu
The buttons and links included in the Landing Page are configured in Navigation Menus. The Top Header Public Menu is the default Navigation Menu for Landing Pages.
Go to Design > click Navigation Menus > select Top Header Public Menu
Select New on the Menu Items page. In the Menu Item type field, select Single Sign-On (Assorted Links and Landing Pages dropdown).
Select a Single Sign-On integration.
Click Save.
The SSO Link is now included in this Navigation Menu.
Include the Navigation Menu on the Landing Page
Next, ensure the Landing Page includes the correct Navigation Menu.
In the editor of the Landing Page, view the Header Section tab. The Top Header Public Menu defaults as the Menu.
Learner Experience
With the Landing Page configured to include all the Menu Items from Top Header Public Menu, the SSO option is displayed at the top of the Landing Page.
Logging in via SSO may utilize some profile information from the SSO directory. View the User Profile Field Mapping and User Group Mapping articles for additional information.