I believe that you can configure how long a ticket is valid. I had this problem in "debug" mode. If I hit a break point in my application, then it would fail because the ticket would time-out. I was told that I should set the value to very long while debugging, and then set the value to a small number that was still reliable. The numbers I was quoted were much less than a second. Just repeating what I was told and what happened to me.
-----Original Message----- From: Andrew Morgan [mailto:[email protected]] Sent: Tuesday, November 11, 2014 11:57 PM To: [email protected] Subject: Re:[cas-user] CAS4 return Ticket 'ST-xxxx' not recognized in Saml11TicketValidator Remember, Service Tickets are only valid once and only for a very short period of time (5 seconds I think). You can't "replay" the same ST. Andy On Tue, 11 Nov 2014, jeffrey tan wrote: > additional: > > when i debug and breakpoints, this problems keep recurring. > However, when i disable all the breakpoints, and i go to client > application again,like localhost:8443/opscentral/, then will re-get > the service ticket and validate success. > from my view, i may thinking this is related to the service ticket > life time. > > > On Wednesday, November 12, 2014 10:45:23 AM UTC+8, jeffrey tan wrote: >> >> the flow is like that, when i access client application, it redirect >> to >> CAS4 login page, after login, it will return service ticket to client >> application, >> >> then it stuck at >> https://localhost:8443/opscentral/login?ticket=ST-4-Ydz5t2YSA01HzR664 >> SrQ-cas01.example.org >> show me blank page. >> >> therefore i breakpoint debug it, i found that CAS4 return me >> >> <?xml version="1.0" encoding="UTF-8"?> <SOAP-ENV:Envelope >> xmlns:SOAP-ENV=" >> http://schemas.xmlsoap.org/soap/envelope/";><SOAP-ENV:Body> >> <saml1p:Response xmlns:saml1p="urn:oasis:names:tc:SAML:1.0:protocol" >> IssueInstant="2014-11-12T01:40:46.574Z" MajorVersion="1" MinorVersion="1" >> Recipient="https://localhost:8443/opscentral/login"; >> ResponseID="_609bad71a819f013ce03be1e11e286e9"><saml1p:Status> >> <saml1p:StatusCode >> Value="saml1p:RequestDenied"/><saml1p:StatusMessage>Ticket >> 'ST-10-ezYO9OgNYseArZmMRCct-cas01.example.org' not recognized >> </saml1p:StatusMessage> >> </saml1p:Status></saml1p:Response></SOAP-ENV:Body> >> </SOAP-ENV:Envelope> >> >> So i back to CAS4 and check it. i found the service ticket is >> correct, but i dont know why it return me ticket null after next line >> as following picture >> >> >> <https://lh6.googleusercontent.com/-gRoFJ9xQHQQ/VGLI_kmdQuI/AAAAAAAAB >> bs/lk-tNI6hy3c/s1600/cas.png> >> >> >> >> > -- > 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
