1 / 26

Grouproles at RUC

Course enrollment based on composite grouproles in external groups. Grouproles at RUC. How do we integrate? Why using groups and roles? Overview of slides: Use Cases presentation Technical infrastructure Group-roles and Portalino Sakai and Providers. Overview.

brone
Download Presentation

Grouproles at RUC

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Course enrollment based on composite grouproles in external groups Grouproles at RUC

  2. How do we integrate? Why using groups and roles? Overview of slides: Use Cases presentation Technical infrastructure Group-roles and Portalino Sakai and Providers Overview

  3. Using LDAP as middle ground for expressing memberships. Access - Step One: Ask for groups for user - Step Three: Find intersection Maintain Access Access - Step Two: Ask for groups for group Maintain

  4. Group-Roles pairs expresses membership of a given group real-world binding to a specific role Role Mapping depends on context of group-role Using Group-Roles

  5. Uses Cases are diverse For teachers: Sakai is voluntarily Support is face2face For students: Teacher chooses Sakai Support is by mail Scenario:Use Cases and Setting

  6. Research teams Special Interest Groups Commitees Organizational Units Student Project Groups Other uses of Sakai

  7. User Directory implemented 10y ago Fully implemented as primary directory New Group-Role database in roll-out Designed and coded 2y ago Continuously pushed as primary directory Still in redesign process Group Management

  8. LDAP as directory protocol User Directory as regular LDAP Group Directory as meta-LDAP Yale CAS as SingleSignOn (SSO) Zero-Effort Cassification Infrastructure

  9. Custom LDAP Schema Strands organize information Highly Agile presentation layer LDAP Development

  10. Rewritten Yale CAS 2.10 Integrated in all Internet Services campus wireless (Blue Socket) Redirects login CAS Development

  11. No CAS (OOTB LDAP provider)

  12. Yale CAS 2.0 unmodified

  13. Zero-Effort Cassification

  14. Memberships in groups formal, informal, and ad hoc for mail-lists,courses, ACLs informative, no business logic nested membership in development GroupRole Database

  15. Resembles reverse DNS <dot> separated Role appended for users <slash><role> suffix Attributes: on groups, e.g.. display name on users, e.g.. guest status DK.RUC.ALFA.SMPL.FALL2006.101 displayName: “SAMPLE 101, FALL 2006” DK.RUC.ALFA.SMPL.FALL2006.101-TEACHER Ms. Andrews DK.RUC.ALFA.SMPL.FALL2006.101-ENROLLED Cindy Diana, enlisted: “Beta Faculty” DK.RUC.ALFA displayName: Sample at Alpha Faculty DK.RUC.ALFA-FACULTY Ms. Andrews, Ms. Brown DK.RUC.ALFA.SMPL-STUDENT Cindy

  16. Light-weight Portal Online bookmarks Some links are pushed to users Everything else is user-land Portalino

  17. Portalino, Screenshot

  18. Wireless defaults to Portalino Links to all services from Portalino Current courses linked directly Archived courses can be hidden Integration

  19. Sakai atRoskilde University

  20. November 2004, Sakai 1.0 in Pilot Manual group administration September 2005, Sakai 2.0 in Production Webservice synching July, 2006 Sakai 2.2 in Production Webservice synching with Group Providers Roadmap

  21. Potential user-base: 8.100 students 1324 staff (also part time) Actual users: 1217 unique session_user Staffing: 1 project leader, 3 admin/devs approx. 1-2 man years User base and staffing

  22. How it should work How it works What we wanted The Group Provider

  23. Standard provided groups

  24. getGroupRolesForUser when generating sites getRole at entry in site getUserRolesForGroup at emails, list of participants unpackId - ? String getRole(id, user) Map getUserRolesForGroup(id) Map getGroupRolesForUser(userId) String[] unpackId(id)

  25. getGroupRolesForUser at login, data cached getRole never! (worksite setup) getUserRolesForGroup at emails, list of participants unpackId - not necessary String getRole(id, user) Map getUserRolesForGroup(id) Map getGroupRolesForUser(userId) String[] unpackId(id)

More Related