Presentation on theme: "EVERY CONNECTION has a starting point. EVERY CONNECTION has a starting point. WorldCat Navigator - Authentication Library Hosted Navigator EZproxy and."— Presentation transcript:
EVERY CONNECTION has a starting point. EVERY CONNECTION has a starting point. WorldCat Navigator - Authentication Library Hosted Navigator EZproxy and Patron Data Server Benefits of Navigator EZproxy Authentication Process Next Steps
What are the benefits of using Navigator? Automates many routine ILL tasks Single Discovery and Delivery Solution for users Users place their own ILL requests All material types are discoverable
To automate some tasks and enable users to place requests, we use EZproxy to manage authentication.EZproxy To automate some tasks and enable users to place requests, we use EZproxy to manage authentication.EZproxy Why EZproxy? How does the authentication process work? What does my library need to do to set up EZproxy? What will OCLC do for me? What is the Patron Data Server? What are the basics I should know?
Why EZproxy? EZproxy deployed in thousands of libraries EZproxy was chosen to fill the user authentication requirement of WorldCat Navigator because of its flexibility. EZproxy is able to authenticate to various external sources such as SIP/SIP2, III Patron API, LDAP, CAS, Shibboleth, formatted flat file and others methods
How does authentication work? Demonstration
How does authentication work?
What are the basics I should know before setting up EZProxy for my library? The authentication process is ultimately set up to return patron details to the WorldCat Navigator services: Patron Full Name – format may be comma-delimited or two separate fields (first name, last name) Patron Barcode from Librarys System (ILS) Patron Address – used to send status alerts to patrons; if no address then no alerts Patron Home Location – used when the library has multiple home locations Patron Banned Flag – what tells Navigator that a patron is disallowed for requesting Optional Fields – Patron Category, Patron Registration Date, and Patron Account Expiration
What are the basics I should know before setting up EZProxy for my library? If your location will ever participate in circulation integration, it is critical that you use the patron ILS barcode during the authentication process. Please note: Key data must be shared between multiple authentication/authorization sources to be able to chain them together. Usually this will be the ILS barcode.
What do I need to do? 1.Work with your OCLC Identity Management lead to determine the EZproxy authentication method(s) suitable to your environment (LDAP, SIP, etc.). Note: It is possible to chain together more than one authentication method; however, ILS barcode or some other common data must tie one method to the other. 2.Ask for an order form from your OCLC Identity Management lead. 3.Complete and submit the order form. 4.Receive your librarys EZproxy license key. 5.Download EZproxy by pointing your Internet browser at: 6.Install EZproxy 7.Protect EZproxy with an SSL certificate.
What do I need to do? 8.Open your librarys EZproxy URL to the world. (Firewall change will be needed.) 9.Work with your OCLC Identity Management lead to configure EZproxy for authentication use with WorldCat Navigator (config.txt). 10.Work with your OCLC Identity Management lead to configure EZproxy to connect to the external authentication resource (user.txt). (LDAP, SIP, etc.) 11.Optionally, customize EZproxy HTML pages for your local requirements. 12.Provide test patron barcodes (credentials) to your OCLC Identity Management lead for testing. 13.Test
What does OCLC needs to do? 1.An OCLC identity management lead will be assigned to your library and be available to discuss specific authentication needs with you. 2.OCLC will provide EZproxy configuration assistance, such as documentation and participation in teleconferences with library IT and Network staffs or with third-party agencies like city IT departments or ILS vendors.
What are the resource needs for EZproxy? To install Ezproxy, these are the requirements: Application foot print = approximately 5 MB Application log data = estimated 100 MB for log files Memory = approximately 70 MB CPU Usage = minimal at less than.5% Patron User Text Files = 1024 Bytes per patron