Developer Area/Specifications in Development/Moving between SSO institutions

From Mahara Wiki
< Developer Area‎ | Specifications in Development
Revision as of 14:53, 24 May 2011 by Hughdavenport (talk | contribs) (Created page with ";ToDo This will show a workflow of how you would move users between different institutions with SSO capabilities. There are three different types of moves. * Simple -> SSO * S…")
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to navigation Jump to search
ToDo

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

There are three different types of moves.

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

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.


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


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


Multiple SSO

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