Verifying Patrons By Using an External LDAP Server
If your organization has acquired the External Patron Verification product, patrons can be verified by an external LDAP server. The patron provides to the Innovative server the information required for verification on the LDAP server—for example, a login and password. The Innovative server forwards the information to the LDAP server.
If the LDAP server verifies the patron, it returns a value to the Sierra server. This value must be the contents of a unique, indexed field in the patron's record—for example, barcode, University ID, or Social Security Number. The Innovative server locates the patron's record.
If the LDAP server does not verify the patron, the patron is directed to verify through patron records on the Innovative server. If the Innovative server verifies the patron, it checks the patron's P TYPE. If the P TYPE is included in the NON_LDAP_PTYPES element of the External Patron Verification configuration file, the system verifies the patron. Otherwise, the system refuses patron verification.
The patron verification forms in the WebPAC allow patrons to enter the information required for verification by either:
- the Innovative server and local patron records
- the LDAP server
Examples of the customizable patron verification forms for organizations using External Patron Verification are available in the example set of library customizable files on CSDirect. The following files are included:
- pverify_web_extpat.html
- pverify_web2_extpat.html
- pverify_web3_extpat.html
- pverify_web4_extpat.html
- pverify_web6_extpat.html
- acquire_web_extpat.html
- illbook_extpat.html
- illchapter_extpat.html
- illdissert_extpat.html
- illgov_extpat.html
- illjournal_extpat.html
- illreport_extpat.html
To customize external patron verification files:
- Edit the files in your local directory.
- Rename the forms by removing the "_extpat" portion of the name.
- Transfer the files to the staging/screens directory on the WebPAC server for testing.
- When testing is completed, transfer the files to the live/screens directory.
The P TYPE field in a patron's record must match one of the designated P TYPEs for the chosen verification method. For example, if the patron attempts verification by using the Innovative server and local patron records, but LDAP verification is required for patrons of the patron's P TYPE, a message displays to the patron and verification fails.
External Patron Verification works with the following optional security protocols:
- Secure Sockets Layer (SSL)
- Transport Layer Security (TLS)
- Simple Authentication and Security Layer (SASL)
- an LDAP password
External Patron Verification and INN-Reach
If your organization contributes to an INN-Reach System, the INN-Reach Central Server can offer your patrons site-specific External Patron Verification prompts during the patron verification process.
When patrons validate on the INN-Reach Central Server, they select their site from the Web Access Management Patron Verification form (pverify2_web.html). The INN-Reach Central Server returns the INN-Reach Central Server Patron Verification form (pverify_inst.html) for access verification or the Request Verification form (pverify3_web.html) for requesting. If your site uses External Patron Verification, these forms can offer validation prompts customized for your site using the appropriate INN-Reach Central LDAP Authentication form.
Enabling Customized External Patron Verification Prompts for INN-Reach
The Central System Administrator maintains the INN-Reach Central LDAP Authentication forms on the INN-Reach Central Server. To enable customized INN-Reach patron verification prompts for your patrons, contact your Central System Administrator.