After login, the CAS server is merely using the browser to redirect. The server itself isn't calling back.
Cheers, Scott On Fri, May 21, 2010 at 8:38 AM, João Galaio da Silva < [email protected]> wrote: > This is strange, because i can make the callback to galaio after login, > with exactly the same url. > > By the way, client and server(cas) need to be trusted by each other? > > I only have the server in ssl and the client with the server certificate. > > > Thanks, > Galaio > > > On Fri, May 21, 2010 at 12:54 PM, Marvin Addison <[email protected] > > wrote: > >> > 2010-05-21 03:31:48,896 WARN [org.jasig.cas.util.HttpClient] - Socket >> > Timeout Detected while attempting to send message to >> > [ >> http://galaio:8012/testescas/OtherServlet;jsessionid=2F24A43D7406A513175C06766A538AD5 >> ]. >> > >> > Is that last log the reason i can't logout? >> >> Yes. The client must be reachable by the same URL originally used to >> request a service ticket for that application. The hostname "galaio" >> is likely unreachable by CAS or firewalled on port 8012; I think a >> socket timeout is more likely caused by a firewall that simply drops >> SYN packets from unrecognized sources. Also beware of SSL trust >> issues as I mentioned earlier. >> >> 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 > > -- 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
