Derek, You will see this error when the value of the "service" request parameter presented to CAS at /cas/login?service= does not exactly match the value of the "service" request parameter on the request for ticket validation at /cas/serviceValidate?service= (or /cas/proxyValidate?service= ).
It is far more likely that your application or possibly CAS instance is misconfigured than that you're encountering a bug in CAS itself. You might turn up the logging in both CAS server and CAS-using application and take a careful look at those request parameters. Andrew http://support.unicon.net/ Derek Ethier wrote: > Tomcat 5.5.20 > CAS 3.0.5 > phpCAS 0.5.1 > > With debug enabled for phpCAS I'm getting the following error on re-direct > back > to the calling service once authenticated. I suspect that it is something > misconfigured in CAS itself, but I can't seem to figure it out. > > <cas:authenticationFailure code='INVALID_SERVICE'> > ticket 'ST-2-7fo7TJ3cLAvPRYcxdaE0NiXpANG0ZvECCLh-20' does not > match supplied > service > </cas:authenticationFailure> > > Is this particular issue solved in CAS 3.0.6 (and soon to be 3.0.7)? Or, is > this related to something else? Any assistance would be appreciated. > > d. > > _______________________________________________ > Yale CAS mailing list > [email protected] > http://tp.its.yale.edu/mailman/listinfo/cas > _______________________________________________ Yale CAS mailing list [email protected] http://tp.its.yale.edu/mailman/listinfo/cas
