93 Login
- Request
- 93
- Response
- 94
- Set
- core
- Position in BX
- 6
Whether a login is required is for the library system to decide – SIP2 expressly leaves it open. If one is required, the login is the first message after opening the connection, and only then does the system answer functional requests. If none is required, the device starts straight away with the system status.
A device should therefore have a setting for whether it logs in.
Request 93#
93<UID algorithm><PWD algorithm><CN...><CO...><CP...>
| Field | Length | Required | Content |
|---|---|---|---|
| UID algorithm | 1 | yes | encryption of the user id; always 0 for none |
| PWD algorithm | 1 | yes | encryption of the password; always 0 for none |
| Identifier | Required | Content |
|---|---|---|
CN |
yes | login user id of the device |
CO |
yes | login password of the device |
CP |
no | location code of the device, e.g. Entrance or North branch |
User id and password travel in clear text. The interface therefore belongs on the library's own network and not on the open internet.
Response 94#
94<ok><user id><password><location><AF...><AG...>
| Field | Length | Required | Content |
|---|---|---|---|
| ok | 1 | yes | 1 logged in, 0 refused |
| user id | 1 | no | 1 user id matches, 0 wrong |
| password | 1 | no | 1 password matches, 0 wrong |
| location | 1 | no | 1 location accepted, 0 unknown |
| Identifier | Required | Content |
|---|---|---|
AF |
no | message for the screen |
AG |
no | message for the receipt |
The three individual positions are an extension of this profile; SIP2 knows only the result. They help when setting up a device, because it is immediately clear which of the three values does not fit. A device that evaluates only the first position works unchanged.
A check left unconfigured counts as passed: If no password is stored in the library system, the password transmitted is not checked.
Example#
9300CNsc-entrance|COsecret|AY0AZF4DB<CR>
941111AFLogin successful|AGLogin successful|AY0AZEEB1<CR>