Integrations/
Single sign-on (SSO) and identity
OneLogin logo
Single sign-on (SSO) and identity

OneLogin single sign-on integration

Learners and admins sign in to Intellum with their OneLogin account, so IT manages access to learning next to the other apps it governs there. OneLogin connects through SAML 2.0 or OpenID Connect, and IT and an Intellum admin set it up with Intellum.

How it connects
Native via SAML 2.0 or OpenID Connect
Who sets it up
IT and an Intellum admin, with Intellum
What moves
One-way: identity from OneLogin to Intellum

Common uses of the OneLogin integration

  • Admins skip manual account setup, since accounts can be created the first time a person signs in.
  • Admins remove accounts through the Intellum API or a recurring user file as part of offboarding.

How the OneLogin integration works

OneLogin connects to Intellum through SAML 2.0 or OpenID Connect. People sign in through OneLogin, and OneLogin 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 OneLogin integration

IT connects OneLogin, and an Intellum admin sets up sign-in for your site with Intellum.

  • A OneLogin account 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
Security and IT

How the Intellum and OneLogin integration handles access and data

  • Authentication: SAML 2.0 or OpenID Connect between OneLogin 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.
SOC 2 Type II
Controls audited by an independent CPA firm
AES-256 encryption
AES-256 at rest and 256-bit TLS in transit
AWS hosting
In the US, with an EU hosting option in AWS Ireland
Enterprise sign-in
SAML 2.0, OAuth 2.0, OpenID Connect, LDAP and ADFS
Read the security, privacy and architecture summary

What to know about the OneLogin 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 OneLogin integration

Does Intellum support OneLogin single sign-on?

Yes. Learners and admins sign in to the LMS with their OneLogin account, and IT and an Intellum admin set up sign-in with Intellum.

OneLogin connects through either SAML 2.0 or OpenID Connect. At sign-in, OneLogin 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 OneLogin setup.

A OneLogin account 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 OneLogin integration working with your stack

Walk through this integration, and the questions IT will ask, with an Intellum expert.