| 2023-05-05 16:17:48 |
Josh Stompro |
description |
Hello, Our state wide ILL resource sharing system asked us if we would like to consider using NCIP for patron authentication instead of using SIP2. Lake Agassiz Regional Library out of Moorhead MN and Minitex in MN, with the mnlink.org resource sharing system.
I think this is done using the LookupUser message which would include an AuthenticationInput entity. One entry for the barcode and then one entry for the password/pin.
Jeff Davis was kind enough to share with me an example of how iNCIPit (NCIP V1) handles it.
https://git.evergreen-ils.org/?p=working/random.git;a=commitdiff;h=11da1d420d7ade35cb5efa37c266a4c76bc3da1b;hp=baf9acde133a0e8f22f699c99e30985130f5d768
It probably needs a config option to specify if all LookupUser request are required to have a pin/password, or if it is just evaluated if it exists in the request.
There is also the AuthenticationPrompt element that seems to be to pass on what fields NCIPServer would want for authentication. That looks like it would be part of the LookupAgencyResponse message. LookupAgency doesn't look like it is currently implemented. |
Hello, Our state wide ILL resource sharing system asked us if we would like to consider using NCIP for patron authentication instead of using SIP2. Lake Agassiz Regional Library out of Moorhead MN and Minitex in MN, with the mnlink.org resource sharing system.
I think this is done using the LookupUser message which would include an AuthenticationInput entity. One entry for the barcode and then one entry for the password/pin.
Jeff Davis was kind enough to share with me an example of how a custom TADL fork of iNCIPit (NCIP V1) handles it.
https://git.evergreen-ils.org/?p=working/random.git;a=commitdiff;h=11da1d420d7ade35cb5efa37c266a4c76bc3da1b;hp=baf9acde133a0e8f22f699c99e30985130f5d768
It probably needs a config option to specify if all LookupUser request are required to have a pin/password, or if it is just evaluated if it exists in the request.
There is also the AuthenticationPrompt element that seems to be to pass on what fields NCIPServer would want for authentication. That looks like it would be part of the LookupAgencyResponse message. LookupAgency doesn't look like it is currently implemented. |
|
