SelfCheck: setting up authentification on SIP2 server?
- Article Type: General
- Product: Aleph
Problem Symptoms:
The SelfCheck machine is working without authentification
How can staff login be activated?
Is there a possibility to check the patron pin?
Cause:
Configuration
Resolution:
The Aleph SIP2 server is working in compliance with SIP2 protocol as defined by 3M
(http://multimedia.3m.com/mws/mediawebserver?mwsId=SSSSSu7zK1fslxtUm8_9m82Uev7qe17zHvTSevTSeSSSSSS--).
The protocol itself has very few functionalities regarding authentification. But these functionalities are fully supported in Aleph:
a. Aleph is supporting protocol message 93 (Login). The "login user id" and the "login password" is checked against the staff permissions in Aleph. If a staff user exists in active library having permission SIP2/GLOBAL, Aleph will sent back response 94 (Login response) with ok = 1.
If there is a problem, response 94 will be ok = 0.
b. You can define pin_required = Y in tab_sip2.conf. Then each patron is expected to supply their password in SIP2-messages 23 (Patron Status Request), 35 (End Patron Session), 37 (Fee Paid) and 63 (Patron Information).
Additional Information
As SIP2 protocol is a session less protocol Aleph can *not* force the SC machine to use message 93 prior any other request. Also Aleph can not prevent that additional requests will be sent after a failed message 93. This must be managed by SC machine and not by Aleph.
Category: Circulation/ALEPH
Subject: Self check (500) - ALEPH
- Article last edited: 11/20/2013