Aaron, From my recent experience, you will want to avoid ISAPI filters as there is a bug that doesn’t work with Chrome. It has to do with in properly terminated headers. UC Davis has updated their code to fix this, but there are questions about support from them.
I ended up doing some testing and was able to use the .Net client to provide authentication in front of IIS7 and greater. Here is an article on how to do it. -John https://wiki.jasig.org/pages/viewpage.action?pageId=35389878 From: Aaron Grant [mailto:[email protected]] Sent: Thursday, September 25, 2014 11:11 AM To: [email protected] Subject: [cas-user] CAS ISAPI Filter / Encoded Service URL Hi Everyone, We have a vendor who has selected the ISAPI Filter on this page: https://wiki.jasig.org/display/CASC/ISAPI+Filter (the zip file that is linked) They are now having issues when the request comes back from our CAS Server (v3.5) with a valid ticket the URL is still URL Encoded. Example: http://host/file.aspx%3ff%3d8CgAAg4D I was wondering if anyone had some insight on this issue. I have some ideas of what might be going on, but it would be nice to hear some other opinions. Thanks! -- Aaron Grant Senior Applications Architect Oakland University - UTS<http://oakland.edu/uts> -- You are currently subscribed to [email protected]<mailto:[email protected]> as: [email protected]<mailto:[email protected]> To unsubscribe, change settings or access archives, see http://www.ja-sig.org/wiki/display/JSG/cas-user -- 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
