1. ISIS to Shibboleth Migration
Datta Mahabalagiri November 18, 2008

2. Today’s Goals Migration guide Difference b/w ISIS & Shibboleth
User experience
Data, Privacy
Migration Roadmap

3. Migration Guide
Migration Guide
Shibboleth Set Up Planning Guide
Hardware, Software, Resource, Time
Will Shibboleth provide all the services my app needs?
User experience
Platform supported?
Special considerations

4. ISIS & Shibboleth ISIS Shibboleth Proprietary Requires coding
Open Source
No coding
Runs as part of app
Application unaware
Web Server + Shibd
UCLA only
Federated
Interoperable outside Ucla
No privacy control
Fine grained Privacy control
Campus adaption
Worldwide adaption in higher education
Not standards based
SAML based
Most Platforms (web service client)
Platforms where you can run Apache/IIS

5. Logon ID UCLA Logon Transition from QDB/OASIS to UCLA Logon
Rethink persistent primary identifier
Think users – students, faculty, staff, guests, alumni

6. User Experience Browser redirect, post, javascript Cross domain
Troubleshooting
Helpdesk support

7. Data and Privacy Who owns data –Registrar’s, HR, Individual
Approval for data release
Protect data in transit, Protect data in storage
Legal Compliance: FERPA, UCLA privacy policies
Privacy control
Person, Group, Enrollment…

8. Migration Roadmap Jan 2009 to Dec 2009 ISIS service ends Dec 2009
Test & Production
Give yourself enough time
Phased migration

9. Resources
Internet2 Shibboleth Wiki:
3 cool demos of how Shibboleth works:
Middleware Infrastructure Team Website: