On 12/11/2017 01:06 PM, Mike Rylander wrote:
> Josh,
>
> It might be better added this to the Evergreen driver, which is
> ILS-aware, to avoid pain down the road when SipServer eventually
> changes. It could be driven (heh) by an chunk
> in the config file, or perhaps as a new attribute on the
t;
>
> *From:* Open-ils-general [mailto:open-ils-general-
> boun...@list.georgialibraries.org] *On Behalf Of *Josh Stompro
> *Sent:* Thursday, December 07, 2017 2:20 PM
> *To:* Evergreen Discussion Group <open-ils-general@list.
> georgialibraries.org>
> *Subject:* Re: [O
Discussion Group <open-ils-general@list.georgialibraries.org>
Subject: Re: [OPEN-ILS-GENERAL] SIP2 - Block certain patrons from
authenticating for a particular login - Evergreen End
This sender failed our fraud detection checks and may not be who they appear to
be. Learn about spoofing<h
...@list.georgialibraries.org] On Behalf Of Josh
Stompro
Sent: Thursday, December 07, 2017 11:47 AM
To: 'Evergreen Discussion Group' <open-ils-general@list.georgialibraries.org>
Subject: [OPEN-ILS-GENERAL] SIP2 - Block certain patrons from authenticating
for a particular login - Evergre
Hello, Has anyone come up with a way of controlling authentication via sip2 on
the sip2 server side for particular users or types of users?
We have various different services that authenticate via sip2, such as our
patron management (cassie), Overdrive, and our state ILL system (MNLINK). The
