Welcome to the 20th Anniversary of the IUG

Rick Paladino – Director, Installation Services Authenticating Users: SSO, LDAP, and Millennium Integrated Patron Login Rick Paladino – Director, Installation Services

SSO: What is Single Sign-On? Users authenticate once per session Log into first server visited Next servers already authorized Enhanced user experience Integrate servers into campus* computing environment

SSO: How It Works User begins session on “participating” server Authenticate against central server Use campus-wide credentials Central login page Auth server creates “session” User “logged in” to all servers

Diagram of SSO Encore SSO Campus other Patron

SSO: Interested in Single Sign-On? Existing SSO initiative Millennium becomes participating server Apache-compatible SSO module CAS Pubcookie Shibboleth Existing SSO initiative 1. III doesn’t help launch SSO for entire institution 2. Becomes another participating member of SSO

SSO: Implementing Single Sign-On Provide SSO module New Millennium SSO server becomes “catalog” DNS change for Millennium server REMOTE_USER and indexed field Still use Millennium patron records Patron load table Re-indexing included

SSO: New Server Becomes “catalog” New Single Sign On web server Change DNS entry for Millennium server Community borrowers access Millennium

SSO: Single Sign-On Recap Central Authentication Server Single Sign-On application Log in using campus-wide credentials Authenticate once per session Integrate existing SSO module into Apache Introduce new Millennium catalog SSO server Enhanced user experience

LDAP: External Patron Verification Log in using campus-wide credentials Authenticate against central server Integrate Library into campus* computing environment

LDAP: Implementing LDAP Existing LDAP server Connection information IP address Bind and search Access account Indexed field Still use Millennium patron records

LDAP: New Login Page

LDAP: External Patron Verification Recap Log in using campus-wide credentials Provide connection information Millennium as LDAP client Still use Millennium patron records Enhanced user experience

SSO and LDAP: Similarities Login using campus credentials Require existing initiatives Provide access to Millennium patron records Support for community borrowers Integrate library into campus computing environment

Authenticating Users: Thinking of SSO? SSO is more evolved More features New server for library Library provides SSO application Big initiative for your institution Are you ready?

Authenticating Users: LDAP may be the First Step Easy to implement User directory already in place Broad support Any LDAP v3 target Microsoft AD No new servers Millennium server is client

IPSSO: Millennium Integrated Patron Login Mini-SSO for Innovative applications WebPAC Encore Research Pro Users authenticate once per session CAS-based application

Integrated Patron Login: Without IPSSO

Integrated Patron Login: Using IPSSO

Millennium Integrated Patron Login Required for Encore and Research Pro Default login for New Libraries Optional login for WebPAC for Existing Libraries New login page

IPSSO: HTML-based form New with 2009B 1.1 Easier customization Support for Airpac for Smartphones Request installation on CSDirect Migration from XML-based form New IPSSO with WebPAC Innovative customizes form upon installation

IPSSO: HTML-based form

IPSSO: Mobile version HTML-based form

Integrated Login: IPSSO with SSO and LDAP SSO login Central Single Sign-On page SSO supersedes IPSSO Use campus credentials to log in once User logged into WebPAC, Encore, RPRO, plus all those others… LDAP login LDAP IPSSO login page Use campus credentials to log in User logged into WebPAC, Encore, RPRO

Integrated Patron Sign-On: IPSSO Recap Mini-SSO for Innovative Applications Native authentication for Encore and Research Pro Full integration with WebPAC Support for LDAP authentication HTML-based form with mobile stylesheet

Thank You!