[Building Sakai] FWD: Sakai & Multi-Institutional Support

[Mark Breuker]

Hi,

We use the Sakai user type to distinct between institutions. For example we have a user type student-institute1 and student-institute2. This allows us to create separate my worksites per institute.

However, some things remain difficult to separate. For instance its not possible to create different e-mail notifications per institute. Also when a user's session times out the user is redirected to the Sakai gateway which has either a skin for institute 1 or 2.

Cheers,

Mark

Mark Breuker
Senior Informatie Analist
Tel.: +31 71 5451 203
Leidse Onderwijsinstellingen bv
Leidsedreef 2
2352 BA Leiderdorp
www.loi.nl-----Oorspronkelijk bericht-----
Van: sakai-dev-bounces at collab.sakaiproject.org [mailto:sakai-dev-bounces at collab.sakaiproject.org] Namens Michael Feldstein
Verzonden: zondag 17 oktober 2010 0:07
Aan: Sean Keesler
CC: Sakai Dev
Onderwerp: Re: [Building Sakai] FWD: Sakai & Multi-Institutional Support

The IMS LIS standard for integrating LMSs and SISs was specifically designed to support the multi-SIS use case. Each Person record coming across to the LMS with a SourcedID that includes a code for the particular SIS installation from which the record was sent. Furthermore, that ID has to be persisted in the LMS, according to the standard. So, if your SISs are using LIS to integrate with Sakai, you should be able to figure out which LDAP directory (or other identity management thingie) to authenticate against on a per-ID basis. The bit that is missing is the ability to associate multiple SourcedIDs with each other, which is what would give you single login. Failing some multi-institutional identity management effort, you could create an option for a user to do this manually.

Does that make sense?

- m

--