X-server: "Error in Verification"
- Article Type: General
- Product: Aleph
- Product Version: 20
Problem Symptoms:
When a request is sent to x-server (WWW-X) (for test purposes using an HTTP call), the following error occurs:
<error>Error in Verification</error>
(See Additional Information, below, for detailed example.)
Cause:
z308_verification_type "02" for non-LDAP log-in.
Resolution:
Change the z308_verification_type to "00". (The z308.pdf doc says: "For standard IDs, this field is set to 00. For LDAP verification IDs, this field is set to 02.") (z308 is the Patron ID's table.)
Additional Information
[Detailed Symptoms:]
When the request is sent to the xserver (for test purposes using an HTTP call), the following error occurs:
<error>Error in Verification</error>
http://linc.xxx.edu/X?op=bor-auth&library=XXX50&bor_id=D123456789&verification=4690
But the following request, gets a correct response:
http://linc.xxx.edu/X?op=bor-auth&library=TCC50&bor_id=TCB987654321&verification=NB82282
Both patrons are active at the same college other than the patron status and identification; there appears to be no difference.
Why does the second work while the first doesn't?
[Detailed Diagnosis:]
xxx00 (usr_library) util f/4 shows:
02 z308_rec_key
03 key_type ...............01
03 key_data ...............D123456789
03 user_library ...........
02 z308_verification ........4690
02 z308_verification_type ...02
02 z308_id ..................XXX000363012
02 z308_rec_key
03 key_type ...............01
03 key_data ...............TCB987654321
03 user_library ...........
02 z308_verification ........NB82282
02 z308_verification_type ...00
02 z308_id ..................XXX000341835
Note that the second has z308_verification_type ...00, while the first has z308_verification_type ...02.
Conduct the following tests:
1. change the first to z308_verification_type ...00; confirm that it works;
2. change the second to z308_verification_type ...02; confirm that it fails.
Category: X-server (500)
- Article last edited: 12/10/2013