Okta single sign-on integration
Learners and admins sign in to Intellum with their Okta account, so access to learning follows the rules IT already set in Okta. Okta connects through SAML 2.0 or OpenID Connect, and IT and an Intellum admin set it up with Intellum.
Common uses of the Okta integration
- IT applies the Okta policies it already enforces, such as multi-factor authentication, to sign-in to learning.
- Admins skip manual account setup, since accounts can be created the first time a person signs in.
How the Okta integration works
Okta connects to Intellum through SAML 2.0 or OpenID Connect. People sign in through Okta, and Okta passes an email or other identifier to Intellum that identifies the person.
Accounts can be created the first time a person signs in through SAML or OAuth. Admins remove accounts through the API or a recurring user file.
How to set up the Okta integration
IT connects Okta, and an Intellum admin sets up sign-in for your site with Intellum.
- An Okta organization your IT team manages, using SAML 2.0 or OpenID Connect
- An email or other identifier sent for each person
- A plan for removing accounts through the API or a recurring user file
How the Intellum and Okta integration handles access and data
- Authentication: SAML 2.0 or OpenID Connect between Okta and Intellum.
- Data: sign-in passes an identity assertion, such as an email or identifier, that identifies the person.
- Accounts: accounts can be created at first sign-in through SAML or OAuth. Admins remove accounts through the API or a recurring user file.
What to know about the Okta integration
- Account removal runs through the Intellum API or a recurring user file, so build it into your offboarding steps.
- Bulk user imports accept an OAuth provider value and a user ID, so imported users match the accounts they sign in with.
Questions about the Okta integration
Yes. Learners and admins sign in to the LMS with their Okta account, and IT and an Intellum admin set up sign-in with Intellum.
Okta connects through either SAML 2.0 or OpenID Connect. At sign-in, Okta passes an email or other identifier that identifies the person in Intellum.
Accounts can be created the first time a person signs in through SAML or OAuth, so admins don’t set each one up by hand. Admins remove accounts through the Intellum API or a recurring user file, so plan that step alongside your Okta setup.
An Okta organization your IT team manages, set up for SAML 2.0 or OpenID Connect, plus an email or other identifier for each person. Plan account removal through the API or a recurring user file before launch.
See the Okta integration working with your stack
Walk through this integration, and the questions IT will ask, with an Intellum expert.