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 Job Title field in the LMS might correlate to the job_title 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.
- 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.
- In the Matching fields of iSpring Learn with the external SSO attributes section, connect fields in iSpring Learn and in the SSO service.
When setting up a section, the required fields in the user profile of the iSpring Learn LMS should be taken into account.
In ADFS, in the Outgoing Claim Type column, some field values should be entered manually, for example sub.
Added fields will be synchronized when a user logs in to the LMS. That is to say, the value of the Title field in SSO will be passed to the Job Title field in iSpring Learn.