Matthew Mikitka
2013-12-04 13:56:22 UTC
Hello,
We are working on a hybrid ezproxy authentication solution with
Shibboleth as the primary mechanism, and barcode/lastname (as per
user.txt) as the secondary mechanism, tailored for alumni and community
patrons. I followed the instructions in the ezproxy documentation --
"Routing users to Shibboleth for authentication" -- and the hybrid
approach works, but the /login page routes to user.txt and
/login?auth=shibboleth&url=^U routes to Shibboleth.
Since the majority of users will use Shibboleth, I want the order
switched: /login routes to Shibboleth and /login?auth=XXXXX&url=^U route
to the user.txt file.
Can this be done, or can someone recommend an alternative approach?
Here is the relevant ezproxy documentation entry:
http://www.oclc.org/support/services/ezproxy/documentation/usr/shibboleth.en.html
Thanks,
matt
---
You are currently subscribed to ezproxy as: gee-***@m.gmane.org.
To unsubscribe, send request to ***@itec.suny.edu
We are working on a hybrid ezproxy authentication solution with
Shibboleth as the primary mechanism, and barcode/lastname (as per
user.txt) as the secondary mechanism, tailored for alumni and community
patrons. I followed the instructions in the ezproxy documentation --
"Routing users to Shibboleth for authentication" -- and the hybrid
approach works, but the /login page routes to user.txt and
/login?auth=shibboleth&url=^U routes to Shibboleth.
Since the majority of users will use Shibboleth, I want the order
switched: /login routes to Shibboleth and /login?auth=XXXXX&url=^U route
to the user.txt file.
Can this be done, or can someone recommend an alternative approach?
Here is the relevant ezproxy documentation entry:
http://www.oclc.org/support/services/ezproxy/documentation/usr/shibboleth.en.html
Thanks,
matt
---
You are currently subscribed to ezproxy as: gee-***@m.gmane.org.
To unsubscribe, send request to ***@itec.suny.edu