SIP2: Protocol for self-checkout (UXPROD-1001)

[SIP2-11] SIP2: Login - startup of SC with Sockets connection Created: 19/Nov/18  Updated: 25/Jun/19  Resolved: 18/Apr/19

Status: Closed
Project: sip2
Components: None
Affects versions: None
Fix versions: 1.0.0
Parent: SIP2: Protocol for self-checkout

Type: Story Priority: P1
Reporter: Hkaplanian Assignee: Matt Reno
Resolution: Done Votes: 0
Labels: q1-2019-spillover
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original estimate: Not Specified

Issue links:
Defines
defines UXPROD-1002 SIP2: Protocol for self-checkout - in... Closed
Relates
relates to SIP2-66 End patron session should not clear t... Closed
Sprint: 3Ms-SIP2-61
Story Points: 3
Epic Link: SIP2: Protocol for self-checkout

 Description   

FOLIO should send this message in response to the SC Login message. When used, this message will be the 1st message sent to the SC from FOLIO.

Scenario - Startup of SC with Sockets connection to ACS
1.Library staff starts self-checkout system
2. Establish socket connection on SC
3. Establish socket connection on FOLIO
4. SC sends login message (93) with user id and password
5. FOLIO returns Login response (94) with ok=1 (if user is valid) or ok=0 if not.
6. SC sends Status message (99)
7. FOLIO returns Status response (98)



 Comments   
Comment by Magda Zacharska [ 18/Mar/19 ]

After receiving Login message from SC:
93<UID algorithm><PWD algorithm><login user id><login password><location code>

UID algorithm: 1-char, fixed-length required field; the algorithm used to encrypt the user id.
PWD algorithm: 1-char, fixed-length required field; the algorithm used to encrypt the password.
login user id: variable-length required field Field Id: CN
login password: variable-length required field Field Id: CO
location code: variable-length optional field; the SC location. Field Id: CP

FOLIO will response with:
94<ok>

ok: 1-char, fixed-length required field: 0 or 1. A '1' in this field indicates that the requested action was allowable and completed successfully. A ‘0’ indicates that the requested action was not allowable or did not complete successfully. This field is described in the preliminary NISO standard Z39.70-199x.

Comment by Magda Zacharska [ 19/Mar/19 ]

Here is the link to SIP-2 specs:http://multimedia.3m.com/mws/media/355361O/sip2-protocol.pdf

Comment by Matt Reno [ 18/Apr/19 ]

See: https://github.com/folio-org/edge-sip2/pull/8

Generated at Fri Feb 09 00:14:49 UTC 2024 using Jira 1001.0.0-SNAPSHOT#100246-sha1:7a5c50119eb0633d306e14180817ddef5e80c75d.