Download - Grouproles at RUC
![Page 1: Grouproles at RUC](https://reader033.vdocuments.mx/reader033/viewer/2022051402/5681585f550346895dc5bbea/html5/thumbnails/1.jpg)
Grouproles at RUC
• Course enrollment based on composite• grouproles in external groups
![Page 2: Grouproles at RUC](https://reader033.vdocuments.mx/reader033/viewer/2022051402/5681585f550346895dc5bbea/html5/thumbnails/2.jpg)
Overview
•How do we integrate?
•Why using groups and roles?
•Overview of slides:
•Use Cases presentation
•Technical infrastructure
•Group-roles and Portalino
•Sakai and Providers
![Page 3: Grouproles at RUC](https://reader033.vdocuments.mx/reader033/viewer/2022051402/5681585f550346895dc5bbea/html5/thumbnails/3.jpg)
- Step Two: Ask for groups for
group
- Step One: Ask for groups for user
Access
AccessMaintain- Step Three: Find intersection
AccessMaintain
Using LDAP as middle ground
for expressing memberships.
![Page 4: Grouproles at RUC](https://reader033.vdocuments.mx/reader033/viewer/2022051402/5681585f550346895dc5bbea/html5/thumbnails/4.jpg)
Using Group-Roles
•Group-Roles pairs
•expresses membership of a given group
•real-world binding to a specific role
•Role Mapping
•depends on context of group-role
![Page 5: Grouproles at RUC](https://reader033.vdocuments.mx/reader033/viewer/2022051402/5681585f550346895dc5bbea/html5/thumbnails/5.jpg)
Scenario:Use Cases and Setting
•Uses Cases are diverse
•For teachers:
•Sakai is voluntarily
•Support is face2face
•For students:
•Teacher chooses Sakai
•Support is by mail
![Page 6: Grouproles at RUC](https://reader033.vdocuments.mx/reader033/viewer/2022051402/5681585f550346895dc5bbea/html5/thumbnails/6.jpg)
Other uses of Sakai
•Research teams
•Special Interest Groups
•Commitees
•Organizational Units
•Student Project Groups
![Page 7: Grouproles at RUC](https://reader033.vdocuments.mx/reader033/viewer/2022051402/5681585f550346895dc5bbea/html5/thumbnails/7.jpg)
Group Management
•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
![Page 8: Grouproles at RUC](https://reader033.vdocuments.mx/reader033/viewer/2022051402/5681585f550346895dc5bbea/html5/thumbnails/8.jpg)
Infrastructure
•LDAP as directory protocol
•User Directory as regular LDAP
•Group Directory as meta-LDAP
•Yale CAS as SingleSignOn (SSO)
•Zero-Effort Cassification
![Page 9: Grouproles at RUC](https://reader033.vdocuments.mx/reader033/viewer/2022051402/5681585f550346895dc5bbea/html5/thumbnails/9.jpg)
LDAP Development
•Custom LDAP Schema
•Strands organize information
•Highly Agile presentation layer
![Page 10: Grouproles at RUC](https://reader033.vdocuments.mx/reader033/viewer/2022051402/5681585f550346895dc5bbea/html5/thumbnails/10.jpg)
CAS Development
•Rewritten Yale CAS 2.10
•Integrated in all Internet Services
•campus wireless (Blue Socket)
•Redirects login
![Page 11: Grouproles at RUC](https://reader033.vdocuments.mx/reader033/viewer/2022051402/5681585f550346895dc5bbea/html5/thumbnails/11.jpg)
No CAS (OOTB LDAP provider)
![Page 12: Grouproles at RUC](https://reader033.vdocuments.mx/reader033/viewer/2022051402/5681585f550346895dc5bbea/html5/thumbnails/12.jpg)
Yale CAS 2.0 unmodified
![Page 13: Grouproles at RUC](https://reader033.vdocuments.mx/reader033/viewer/2022051402/5681585f550346895dc5bbea/html5/thumbnails/13.jpg)
Zero-Effort Cassification
![Page 14: Grouproles at RUC](https://reader033.vdocuments.mx/reader033/viewer/2022051402/5681585f550346895dc5bbea/html5/thumbnails/14.jpg)
GroupRole Database
•Memberships in groups
• formal, informal, and ad hoc
• for mail-lists,courses, ACLs
• informative, no business logic
•nested membership in development
![Page 15: Grouproles at RUC](https://reader033.vdocuments.mx/reader033/viewer/2022051402/5681585f550346895dc5bbea/html5/thumbnails/15.jpg)
DK.RUC.ALFAdisplayName: Sample at Alpha Faculty
DK.RUC.ALFA-FACULTYMs. Andrews, Ms. Brown
DK.RUC.ALFA.SMPL-STUDENTCindy
DK.RUC.ALFA.SMPL.FALL2006.101displayName: “SAMPLE 101, FALL 2006”
DK.RUC.ALFA.SMPL.FALL2006.101-TEACHERMs. Andrews
DK.RUC.ALFA.SMPL.FALL2006.101-ENROLLEDCindy
Diana, enlisted: “Beta Faculty”
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
![Page 16: Grouproles at RUC](https://reader033.vdocuments.mx/reader033/viewer/2022051402/5681585f550346895dc5bbea/html5/thumbnails/16.jpg)
Portalino
•Light-weight Portal
•Online bookmarks
•Some links are pushed to users
•Everything else is user-land
![Page 17: Grouproles at RUC](https://reader033.vdocuments.mx/reader033/viewer/2022051402/5681585f550346895dc5bbea/html5/thumbnails/17.jpg)
Portalino, Screenshot
![Page 18: Grouproles at RUC](https://reader033.vdocuments.mx/reader033/viewer/2022051402/5681585f550346895dc5bbea/html5/thumbnails/18.jpg)
Integration
•Wireless defaults to Portalino
•Links to all services from Portalino
•Current courses linked directly
•Archived courses can be hidden
![Page 19: Grouproles at RUC](https://reader033.vdocuments.mx/reader033/viewer/2022051402/5681585f550346895dc5bbea/html5/thumbnails/19.jpg)
Sakai atRoskilde University
![Page 20: Grouproles at RUC](https://reader033.vdocuments.mx/reader033/viewer/2022051402/5681585f550346895dc5bbea/html5/thumbnails/20.jpg)
Roadmap
November 2004,Sakai 1.0 in Pilot
Manual group administration
September 2005,Sakai 2.0 in Production
Webservice synching
July, 2006Sakai 2.2 in Production
Webservice synching with Group Providers
![Page 21: Grouproles at RUC](https://reader033.vdocuments.mx/reader033/viewer/2022051402/5681585f550346895dc5bbea/html5/thumbnails/21.jpg)
User base and staffing
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
![Page 22: Grouproles at RUC](https://reader033.vdocuments.mx/reader033/viewer/2022051402/5681585f550346895dc5bbea/html5/thumbnails/22.jpg)
The Group Provider
•How it should work
•How it works
•What we wanted
![Page 23: Grouproles at RUC](https://reader033.vdocuments.mx/reader033/viewer/2022051402/5681585f550346895dc5bbea/html5/thumbnails/23.jpg)
Standard provided groups
![Page 24: Grouproles at RUC](https://reader033.vdocuments.mx/reader033/viewer/2022051402/5681585f550346895dc5bbea/html5/thumbnails/24.jpg)
String getRole(id, user)Map getUserRolesForGroup(id)Map getGroupRolesForUser(userId)String[] unpackId(id)
getGroupRolesForUserwhen generating sites
getRoleat entry in site
getUserRolesForGroupat emails, list of participants
unpackId - ?
![Page 25: Grouproles at RUC](https://reader033.vdocuments.mx/reader033/viewer/2022051402/5681585f550346895dc5bbea/html5/thumbnails/25.jpg)
String getRole(id, user)Map getUserRolesForGroup(id)Map getGroupRolesForUser(userId)String[] unpackId(id)
getGroupRolesForUserat login, data cached
getRolenever! (worksite setup)
getUserRolesForGroupat emails, list of participants
unpackId - not necessary
![Page 26: Grouproles at RUC](https://reader033.vdocuments.mx/reader033/viewer/2022051402/5681585f550346895dc5bbea/html5/thumbnails/26.jpg)