Pearson
Always Learning

The SAML 2.0 implementation within LearningStudio supports two primary use cases for which both are described in detail below:

 

USE CASE #1 - LearningStudio Campus Access Through Federated Services

In this scenario a user attempts to access the LearningStudio portal directly from the eCollege hosted public campus without being logged on. The user has an account in LearningStudio and a federated account managed by the institution. PingFederate sends an authentication request to the institution's identity provider ("IdP"). Both the request and the returned SAML assertion are sent through the user’s browser via HTTP POST.

  1. User clicks on link to access LearningStudio.
  2. PingFederate sends Authentication Request to the user’s browser that is immediately posted to the IdP to request SSO service.
  3. The IdP authenticates the user.
    1. The IdP will determine if the user has an open session. If not, a logon screen is presented.
    2. The user logs in with their valid credentials.
  4. The IdP validates user credentials against the user store.
  5. The IdP send SAML Response to the users browser that is immediately posted to PingFederate to request Assertion Consumer Service.
  6. PingFederate uses OpenToken adapter to send token to the user’s browser and request the portal launch.
    1. A new service is needed to launch the portal using the OpenToken. The existing service only works with course launch and requires a call number.
  7. User is given access to portal and course list.

 

USE CASE #2 - LearningStudio Course Access Through Federated Services

In this scenario is similar to the process above but the user attempts to access a specific LearningStudio course by clicking on a link within their course listing on the institution’s portal. The user has an account within LearningStudio and a federated account managed by the institution.
 
  1. User clicks on a link within their course list on their university hosted portal.
    1. Steps 1 through 3 can vary depending on portal and IdP configuration.
  2. The portal request the SSO service from the IdP.
  3. The IdP gathers any additional attributes needed for course launch. For LearningStudio course launch, the username, client string (campus identifier), and call number (course identifier) are required.
  4. The IdP send SAML Assertion to the users browser that is immediately posted to PingFederate to request Assertion Consumer Service.
  5. PingFederate uses OpenToken adapter to send token to the user’s browser and request the course launch. The username, client string, and call number are extracted from the assertion and included in the token.
  6. User is given access to their course.

Note: For Use Case #2, the IdP must have the ability to pass the LearningStudio CallNumber in the successful assertion to be able to identify the course to be launched.

2443 reads
Always Learning
Pearson