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.
|
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.
|