Actions

Difference between revisions of "Developer Area/Specifications in Development/Moving between SSO institutions"

From Mahara Wiki

< Developer Area‎ | Specifications in Development
m
Line 14: Line 14:
  
 
Inbetween each transition, we have a parking institution, which is described below.
 
Inbetween each transition, we have a parking institution, which is described below.
 +
 +
An extra option will be added to the Institute->Members screen, where new institute admins can transfer users from parked institutions.
  
  

Revision as of 18:20, 25 May 2011

ToDo

This will show a workflow of how you would move users between different institutions with SSO capabilities.

There are four different types of moves.

  • Simple -> Simple
  • Simple -> SSO
  • SSO -> Simple
  • SSO -> SSO

There is also the case when a user wants to be part of two or more institutions that use SSO.

Inbetween each transition, we have a parking institution, which is described below.

An extra option will be added to the Institute->Members screen, where new institute admins can transfer users from parked institutions.


Simple -> Simple

This is moving users from an internal auth method to another institution that uses internal auth.

The workflow would be as follows:

  1. Original Institute admin sends student to a parking inst using internal auth
  2. credentials don't change
  3. 2nd institute provider uses the Institutions->Members screen to move students from parking to their institution
  4. auth will be the same as the internal auth already set

There could also be a CSV file workflow with the following fields

username, parkedinst

which will take username out of parkedinst

A CSV file with only username field can take users out of institution and put them in the parking one.


Simple -> SSO

This is moving users from an internal auth method to an institution that uses SSO.

This would happen if a student enrols in a school that uses SSO, and they already had a portfolio they want to keep.

The workflow for this would be as follows:

  1. Original Institute admin sends student to a parking inst using internal auth
  2. credentials don't change
  3. 2nd SSO provider uses the Institutions->Members screen to move students from parking to their institution
  4. Mahara will change auth from internal auth to 2nd SSO
  5. * If 2nd SSO has a different username on remote side, they will need to update the user's remote username on mahara


This workflow could also include a CSV file upload with the following contents

username, parkedinst, remoteusername (this field is optional, defaults to username)

This will take the user from the parked inst, and change their remoteusername if supplied.

A CSV file with only username field can take users out of institution and put them in the parking one.

SSO -> Simple

This is moving users from an institution that uses SSO to a simple internal auth method.

This would happen when a student leaves a school for example. They would still want to keep their portfolio

The workflow for this would be as follows:

  1. Original SSO Provider sends student to a parking inst with internal auth
  2. Mahara generates a password for that student that gets emailed to them, changed on first login.
  3. 2nd institute provider uses the Institutions->Members screen to move students from parking to their institution
  4. auth will be the same as the internal auth already set in step 2

There could also be a CSV file workflow with the following fields

username, parkedinst

which will take username out of parkedinst

A CSV file with only username field can take users out of institution and put them in the parking one.

SSO -> SSO

This is moving users from one institution that uses SSO to another institution that uses SSO.

This would happen when a student leaves one school and enrols in another. They want their portfolio to follow them.

The workflow for this would be as follows

  1. Original SSO Provider sends student to a parking institution with internal auth
  2. Mahara generates a password for that student that gets emailed to them, changed on first login.
  3. 2nd SSO provider uses the Institutions->Members screen to move students from parking to their institution
  4. Mahara will change auth from internal auth to 2nd SSO
  5. * If 2nd SSO has a different username on remote side, they will need to update the user's remote username on mahara

This workflow could also include a CSV file upload with the following contents

username, parkedinst, remoteusername (this field is optional, defaults to username)

This will take the user from the parked inst, and change their remoteusername if supplied.

A CSV file with only username field can take users out of institution and put them in the parking one.

Parking Institution

A dummy institution that maps to the old institution, but only uses internal auth.

When a user is put into this institution, they have a password generated if they don't already have one, this is then emailed to them. They are forced to change on first login.


Multiple SSO

  • Wishlist

This happens when a user is part of two institutions that use SSO, and they want their portfolio to be the same in both of them