Thanks, Scott. Can all the clients using serviceValidate consume the customized JSP or will some possibly choke on it?
Anyone out there using such a custom JSP? On Sep 1, 2011, at 9:43 AM, Scott Battaglia wrote: By default /serviceValidate will NEVER said attributes back. It requires a custom JSP. On Thu, Sep 1, 2011 at 12:38 PM, Cary, Kim <[email protected]<mailto:[email protected]>> wrote: Going a little nuts here. We have a working EZProxy integration with CAS. We're trying to do authorization based on attributes that are returned by CAS, but EZProxy is only sending us /serviceValidate ticket checks. The OCLC support folks are saying that we just don't know how to configure our CAS server to return those attributes. I'm saying they must have developed it against some customized/extended CAS server, because what they're sending us will NEVER result in an attribute return. Who is right? (or some other explanation) Is anyone using EZProxy with group authorization by CAS attributes? -- 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]<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
