Martin, I'm not sure I follow what you're asking.
Are you asking about a potential redirect after using /logout (i.e. /logout?service=foo). If that's the case it only works if you've enabled that on the logout controller. If you're asking about errors for the callback of the logout (i.e. notifying each application that the user logged out), then you may have an application that uses a self-signed certificate which may not be in the JVM's cacerts file. -Scott -Scott Battaglia PGP Public Key Id: 0x383733AA LinkedIn: http://www.linkedin.com/in/scottbattaglia On Fri, Aug 15, 2008 at 4:21 AM, Martin Lamprechter < [EMAIL PROTECTED]> wrote: > Hi, > > I use CAS 3.2.1.1 and I guess everything works fine. > But today I have a look at the log-file and I saw many errors like this: > > > PKIX path building failed: > > sun.security.provider.certpath.SunCertPathBuilderException: unable to > > find valid certification path to requested target > > On every logout a new error-log is written. > > Maybe it is something wrong with the logout service-redirectURL - it is > signed, but the cert doesn't match the URL (just testing right now). > But when CAS is so strong with certs, why can I login to the same URL? > > And if everything works fine - should I be redirected to the > ?service-URL? In my case logout ends on the CAS-Logout site.... > > Best regards > Martin > _______________________________________________ > 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
