Scott, One more possible scenario in which this error will occur: 3) "broken" CAS cluster. However, I don't think that this is the issue discussed in this thread.
I couldn't help noticing that the original error message said "ticket 'ST-26-SN8bAqhHS1fHh0XCs9eX' does not match supplied service." The most recent message is different, so we may be looking at two issues. Adam Scott Battaglia wrote: > That particular error generally means that either (a) the ticket > expired or (b) you attended to validate it twice. > > Cheers, > Scott > > > On Wed, Feb 10, 2010 at 5:27 AM, Laura Negre <[email protected] > <mailto:[email protected]>> wrote: > > I have more information on my problem. > > In the file AbstractUrlBasedTicketValidator, the method > retriveResponseFromServer return the following response : > > <cas:serviceResponse xmlns:cas=’http://www.yale.edu/tp/cas’> > > <cas:authenticationFailure code=’INVALID_TICKET’> > > Ticket ‘ST-16-7iLOYZJwmT2IVFlkknqh’ > not recognized > > </cas:authenticationFailure> > > </cas:serviceResponse> > > > > Thanks > > > > *De :* Scott Battaglia [mailto:[email protected] > <mailto:[email protected]>] > *Envoyé :* vendredi 5 février 2010 17:13 > *À :* [email protected] <mailto:[email protected]> > *Objet :* Re: [cas-user] > org.jasig.cas.client.validation.TicketValidationException > > > > Just a note that newer versions of CAS will actually return the > two service urls that do not match. My guess is you're on an older > version of CAS. > > The error probably means that you authentication filter and > validation filter don't match on what is being sent to CAS. > > On Fri, Feb 5, 2010 at 8:40 AM, Marvin Addison > <[email protected] <mailto:[email protected]>> wrote: > > > I have this problem when I connect to CAS. Do you think it’s a > problem with > > LDAP? > > Doubtful it's related to the authentication handler. It's failing > once the client presents the ticket it received from the server for > validation, which would imply a successful authentication previously. > > Your error, "ticket <TICKET_ID> does not match supplied service", > occurs when the recorded service URL in the ticket registry doesn't > match that presented on ticket validation. You should be able to turn > up logging to DEBUG for org.jasig.cas in order to display the service > to which a ticket is granted in the cas.log file. Then you ought to > examine the request made to the CAS server for ticket validation and > compare the service in that request with what's in the logs. I > believe you can turn up org.springframework logger high enough to see > the request parameters in the cas.log file, but you could also use a > request dumper filter, e.g. > > http://code.google.com/p/vt-middleware/wiki/vtservletfilters#RequestDumperFilter, > to dump the request parameters. > > > M > > -- > 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] > <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 -- 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
<<attachment: arybicki.vcf>>
