On 14/12/2012 06:08 μμ, jleleu wrote:
Hi,
I did several tests but I can't reproduce the issue.
I call http://localhost:8080/cas/login?service=http://www.google.fr and log in,
I'm redirected to google with a service ticket.
I wait some time (from a few seconds to several minutes).
I call http://localhost:8080/cas/login?service=http://www.google.fr&renew=true,
I log in and I'm redirected to google with a new service ticket.
The logs look normal.
I did tests on a customized CAS server and on a "re-created from scratch" CAS
server : https://github.com/leleuj/cas-overlay-3.5.x. I use jetty but Tomcat also.
I have no explanation for your problem.
The services management works fine as well.
Can you test with my demo : https://github.com/leleuj/cas-overlay-3.5.x and see
if you can reproduce the issue also ?
Best regards,
Jérôme
Hello Jérôme,
You are right. By using a "fresh" CAS server installation the problem
disappeared. After further investigation I discovered that the root
cause of the problem was the inclusion of a js file that did not really
existed. The absence of this file had the side effect (I can't
understand why) to leave execution value (say e1s1) as is between posts,
so every time (IIUC) user returned to a flow execution state that was
already killed.
Thanks for your time,
Best regards,
Pavlos
--
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
