Ahh thanks, it wasn't clear to me that the Wrapper and Validation filter go together. It's the Validation filter that throws exceptionss due to my SSL cert issues.
We thought that putting the CAS behind a proxy with valid certs would solve that problem, but it didn't. Since we are running our CAS server on a "red box" (i.e. test machine) my boss has no desire to get a valid cert for it. I am sure as we move forward with the project we will be running on boxes with real certs, so for the time being everything is cool. I really appreciate your patience working with me. Thanks again, Bryan -----Original Message----- From: Marvin Addison [mailto:[email protected]] Sent: Friday, July 31, 2009 1:09 PM To: [email protected] Subject: Re: [cas-user] How do I get prinicpal from CASifyed client program? Your web.xml is missing a validation filter definition, e.g. org.jasig.cas.client.validation.Cas20ProxyReceivingTicketValidationFilter, so you're never validating service tickets before entering into your application. ST validation is how the client app gets the principal from the server, which would explain why you have a null principal from request.getRemoteUser(). You're doing a manual ST validation by opening a stream and reading the response, but there are filters that do it for you. See http://www.ja-sig.org/wiki/display/CASC/Configuring+the+JA-SIG+CAS+Client+for+Java+in+the+web.xml for detail on the various filters you need. 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
