1. UIT Campus Systems & Infrastructure CAS Web Authentication

2. go.utah.edu - Then

3. go.utah.edu - Now

4. go.utah.edu – Performance (Before)

5. go.utah.edu – Performance (After)

6. go.utah.edu - Future

7. ulogin.utah.edu - Now Old version of CAS Lack of Service Manager (can be used by anyone) Not redundant Future Upgrade CAS Migrate to mirror go.utah.edu architecture Eventually implement Service Manager

8. go vs ulogin? SSL vs non-SSL But ulogin.utah.edu is SSL right? Sorta. Interesting Thought: Why do you need user login if you don’t need to secure the data? SSO with Enterprise Apps Still better to offer ulogin than having developers handle credentials directly.

9. Questions? cas@lists.utah.edu Helpdesk (581-4000) Campus Web Services queue