Leveraging an existing single sign-on (SSO) system, Cornell University implemented SSO for its digital asset management (DAM) system. The key benefits of adopting SSO for the DAM were to simplify user management, provide immediate access for users without separate logins or passwords, and minimize support time spent on user permissions and registrations. Cornell's existing SSO and user database infrastructure allowed for seamless integration and rapid adoption of the new DAM system across the university.

1. Leveraging Your SSO
Deanna Ballew
with
Corey Chimko

2. What is a Single Sign On
• Simplify user management
• Minimize usernames and passwords
• Removes the obstacle of another login

3. Cornell University Photography
Widen Media Collective Digital Asset Management (DAM) System
photo.cornell.edu

4. Reasons for Adoption
• Enormous potential user base
• User data exists in OHR database
photo.cornell.edu

5. Reasons for Adoption
• Existing SAM/Shibboleth system in place,
only have one password
• Eliminate support time spent on password
retrievals
photo.cornell.edu

6. Reasons for Adoption
• User data mirroring between ‘official’
Cornell data and DAM
• Remove time constraints with processing
user requests
• Immediate access for all users
photo.cornell.edu

7. Implementation
Request for implementation then:
1 Widen Tech + 1 Cornell Security Tech =
photo.cornell.edu

8. Post-Implementation
Processing
• New users
processed in
0 – 10 seconds
• Elevate users
permissions if
needed
photo.cornell.edu

9. What are the benefits
• Minimal time supporting user permissions,
registrations and passwords
• DAM is another application that
Cornellians can utilize
• Rapid and unprecedented user adoption
photo.cornell.edu

10. SSO IS THE WAY TO GO!!
photo.cornell.edu

11. More examples of SSO

12. Managing user permissions
• Set initial user role for new users
• Synch user roles upon each login. User
data passed and updated in DAM.

13. Immediate access
• Users have immediate access, no waiting
for admin approval
• Makes it self service for users, hands off

14. Implementation Process