One thing to keep in mind is that the EZProxy SP implementation is not quite as full-featured as the native Shibboleth SP client. We discovered that EZProxy's SP could not handle chaining attribute authorities, which pretty much ruled that path out for us. So we ended up setting up a simple shib-enabled proxy server application, which does all the authentication and authorization, then passes a verified request along to EZProxy.

But if your use case is simple (all your attributes come from the same IdP that handles the authentication), EZProxy's built-in SP should be fine.

-- Scott

On 05/26/2016 01:39 PM, Michael Berkowski wrote:
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hi all,

We're doing early investigation into switching our hosted ILLiad from LDAP
authentication over to Shibboleth for a few continuity & usability reasons.

Based on my reading of ILLiad documentation, Shibboleth can be accomplished
via a RemoteAuth delegation, but for hosted ILLiad it must go through EZproxy.
That's fine -- we would appreciate the flexibility EZproxy could provide.

https://prometheus.atlas-sys.com/display/illiad/RemoteAuth+Authentication+Process

I would be interested to hear from the community if any of you have delegated
ILLiad's auth through EZproxy, Shibboleth or otherwise, hosted or local
EZproxy.  I've found a few older presentation slides & EZproxy list
discussions on it; setup seems more or less straightforward for EZproxy.  Did
anything catch you by surprise?


Best,
- --
++++++++++++++++++++
Michael Berkowski
University of Minnesota Libraries
m...@umn.edu
612.626.6137
PGP Public Key: http://z.umn.edu/mjbpubkey
++++++++++++++++++++

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1

iEYEARECAAYFAldHQvoACgkQ01KJk46VC2Y3bwCdFAzl6Nfpg5kNOAnIS+UZFII3
3dsAn3luo4pUlbGAqFZaoIE9P2N3vgXC
=6MFU
-----END PGP SIGNATURE-----


--
Scott Prater
Shared Development Group
General Library System
University of Wisconsin - Madison

Attachment: smime.p7s
Description: S/MIME Cryptographic Signature

Reply via email to