Page tree
Skip to end of metadata
Go to start of metadata

When a user logs in to iSpring Learn for the first time with one of single sign-on technologies, their account is created in the LMS. The only field which is always passed to iSpring Learn when authorizing via SSO is the Login field.

If you already have a service for SSO (for example, ADFS or Okta) which can pass user profile fields to iSpring Learn, you may want to make the user profile in the LMS filled out automatically. However, fields in iSpring Learn and in a SSO service could be named differently. For instance, the Education field in the LMS might correlate to the education_stage field in SSO. 

To get all the fields in the user profile filled out correctly, match fields in iSpring Learn and in the SSO service.

  1. Take care of this when initially setting up the SSO technology you picked up or make changes later on the SSO integration settings page.

    Read through detailed instructions on how to enable SAML, JWT and OpenID in your iSpring Learn account.

  2. In the Matching fields of iSpring Learn with the external SSO attributes section, connect fields in iSpring Learn and in the SSO service.



  3. Added fields will be synchronized when a user logs in to the LMS. That is to say, the value of the education_stage field in SSO will be passed to the Education field in iSpring Learn. 

Synchronized data overwrite values previously entered in the profile field manually.
For example, you have entered 'secondary' in the Education field in the LMS. After a user authorizes, the value will be replaced by the value passed by the SSO service, let's say, 'higher'.

If the data wasn't passed or the field name was mistyped, the information in iSpring Learn won't be updated, no error message will pop up.

  • No labels