Hello all, I have read documentation for using CAS with Ezproxy and it seems to agree with some postings on this list. However, I am missing something and thought someone here might want to weigh in.
I have the Ezproxy server registered as a service with CAS. The Ezproxy URL format I am using (and successfully using login directly through Ezproxy) is something like: http://myezproxy.server.com/login?url=http://myresource.com According to the Ezproxy documentation for a CAS implementation: Configuration To enable Central Authentication Service (CAS)<http://www.jasig.org/cas>, edit user.txt/ezproxy.usr and add lines similar to: ::CAS LoginURL http://www.yourlib.org/cas/login ServiceValidateURL http://www.yourlib.org/cas/serviceValidate /CAS By default, the use of CAS disables EZproxy's normal login methods, including the presentation of the login menu. My constructed URL looks something like this: https://mycas.server.com/cas/login?service=http://myezproxy.server.com/login?url=http://myresource.com After doing this, I restart Ezproxy. When I try to access one of the URLs, it takes me to the CAS login page, I log in, and it takes me to the Ezproxy login page. I'm not sure why it is not just taking me to the resource, as I thought this is supposed to disable the normal Ezproxy login method. I tried commenting out the configured login method for Ezproxy, but still it presents the login page. If this is more of an Ezproxy question, I can follow up on that. Many thanks, Christopher Adams -- You are currently subscribed to [email protected] as: [email protected] To unsubscribe, change settings or access archives, see http://www.ja-sig.org/wiki/display/JSG/cas-user
