There is also a "clientAuth" option that essentially says "use it if its presented / the user has one". I'm not sure if that's appropriate in your situation.
On Tue, Jun 30, 2009 at 10:45 AM, Marvin Addison <[email protected]>wrote: > > So i couldnt understand, what should i do as a solution? > > Create another <Connector> element in your server.xml on another port, > e.g. 9443, with clientAuth=false, and point your CAS client validation > URL there, e.g. https://your.host:9443/cas/serviceValidate. > > I can see from the stack trace that you're using the old 2.x Yale > client, which isn't really supported anymore. I would recommend you > upgrade to the latest 3.x client, > http://www.ja-sig.org/downloads/cas-clients/, which has a lot of > documentation and is actively supported. > http://www.ja-sig.org/wiki/display/CASC/CAS+Client+for+Java+3.1 is the > starting point for documentation. > > M > > -- > 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 > > -- 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
