ISIS to Shibboleth Migration Datta Mahabalagiri November 18, 2008
Today’s Goals Migration guide Difference b/w ISIS & Shibboleth User experience Data, Privacy Migration Roadmap
Migration Guide Migration Guide https://spaces.ais.ucla.edu/display/iamucla/IsisShibMigration Shibboleth Set Up Planning Guide https://spaces.ais.ucla.edu/display/iamucla/ShibSPPlanningGuide Hardware, Software, Resource, Time Will Shibboleth provide all the services my app needs? User experience Platform supported? Special considerations
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
Logon ID UCLA Logon Transition from QDB/OASIS to UCLA Logon Rethink persistent primary identifier Think users – students, faculty, staff, guests, alumni
User Experience Browser redirect, post, javascript Cross domain Troubleshooting Helpdesk support
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 http://map.ais.ucla.edu/go/1002622 Privacy control Person, Group, Enrollment…
Migration Roadmap Jan 2009 to Dec 2009 ISIS service ends Dec 2009 Test & Production Give yourself enough time Phased migration
Resources Internet2 Shibboleth Wiki: https://spaces.internet2.edu/display/SHIB 3 cool demos of how Shibboleth works: http://www.switch.ch/aai/demo/ Middleware Infrastructure Team Website: http://spaces.ais.ucla.edu