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 <marvin.addi...@gmail.com>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 cas-user@lists.jasig.org as: > scott.battag...@gmail.com > To unsubscribe, change settings or access archives, see > http://www.ja-sig.org/wiki/display/JSG/cas-user > > -- You are currently subscribed to cas-user@lists.jasig.org as: arch...@mail-archive.com To unsubscribe, change settings or access archives, see http://www.ja-sig.org/wiki/display/JSG/cas-user
