[Deploying Sakai] SIS Integration

Ray Davis ray at media.berkeley.edu
Wed Sep 9 09:27:14 PDT 2009


We do indeed do something similar, although not using Banner. We use a 
materialized view to get SIS and cached LDAP data for most users, use 
Kerberos authentication to login most users, but also allow Sakai-stored 
internal users and passwords. (Of course we also allow project sites!) 
You'll find a pointer to our source code on the Course Management 
Integration tutorial page:

http://confluence.sakaiproject.org/display/SAKDEV/Course+Management+Integration

Best,
Ray

On 9/9/09 8:16 AM, Jason Shao (CampusEAI Consortium) wrote:
> I think  Berkeley does something similar – I believe they have a 
> CourseManagementService implementation that is backed by materialized 
> views against their Banner or a copy of their Banner DB.
> 
> Jason
> 
> On 9/9/09 10:34 AM, "Paul Gibbs" <pgibbsjr at hotmail.com> wrote:
> 
>     It just occurred to me that someone might want to know a little bit
>     more information.
>      
>     Our SIS is stored on a SQL Server database. We would like to have
>     Sakai automatically set up students, profs, academic years, courses,
>     course offerings, and class rosters using the SQL database. That
>     way, if we add a student or drop a student from a class using our
>     SIS, Sakai will reflect that change. Regarding user
>     authentication—our database has user IDs and passwords, but we can’t
>     access the passwords outside of the proprietary software. My thought
>     was to add a custom record to our SIS to store their Active
>     Directory user account, and then authenticate on LDAP and have Sakai
>     retrieve the student information associated in the SQL database with
>     that AD account. (Hope that makes sense!)
>      
>     I would still like to be able to create one-off users and project
>     sites, however, in addition to managing courses using the
>     integration. However, I’m willing to let that go if necessary.
>      
>     Paul
>      
> 
>     *From:* production-bounces at collab.sakaiproject.org
>     [mailto:production-bounces at collab.sakaiproject.org] *On Behalf Of
>     *Paul Gibbs
>     *Sent:* Wednesday, September 09, 2009 10:27 AM
>     *To:* production at collab.sakaiproject.org
>     *Subject:* [Deploying Sakai] SIS Integration
> 
>     Does anyone have any documentation on setting up an SIS with the
>     course management service other than this:
>     http://confluence.sakaiproject.org/display/DOC/Sakai+Admin+Guide+-+Course+Integration
>     <http://confluence.sakaiproject.org/display/DOC/Sakai+Admin+Guide+-+Course+Integration>?
>      
>     I found this:
>     http://confluence.sakaiproject.org/display/SAKDEV/Course+Management+Integration
>     <http://confluence.sakaiproject.org/display/SAKDEV/Course+Management+Integration>,
>     but that was written for 2.4.x. Is this still valid?
>      
>     Thanks,
>      
>     Paul Gibbs
>     CBTS / Lansdale, Pennsylvania
> 
> 
> --
> Jason Shao
> Director of Product Development
> CampusEAI Consortium
> 1940 East 6th Street, 11th Floor
> Cleveland, OH 44114
> Tel: 216.589.9626x249
> Fax: 216.589.9639
> 
> ------------------------------------------------------------------------
> Your input is important to improve upon our continuous efforts to 
> service you better. Please e-mail my manager at anjli_jain at campuseai.org 
> with any feedback.
> 
> CONFIDENTIALITY NOTICE:
> This e-mail together with any attachments is proprietary and 
> confidential; intended for only the recipient(s) named above and may 
> contain information that is privileged. You should not retain, copy or 
> use this e-mail or any attachments for any purpose, or disclose all or 
> any part of the contents to any person. Any views or opinions expressed 
> in this e-mail are those of the author and do not represent those of 
> CampusEAI Consortium or the Open Student Television Network. If you have 
> received this e-mail in error, or are not the named recipient(s), you 
> are hereby notified that any review, dissemination, distribution or 
> copying of this communication is prohibited by the sender and to do so 
> might constitute a violation of the Electronic Communications Privacy 
> Act, 18 U.S.C. section 2510-2521. Please immediately notify the sender 
> and delete this e-mail and any attachments from your computer. Warning: 
> Although precautions have been taken to make sure no viruses are present 
> in this e-mail, the companies cannot accept responsibility for any loss 
> or damage that arise from the use of this e-mail or attachments.



More information about the production mailing list