Thank you very much Misagh, maybe I have to look in the client code to see what happened on the client side with the callback, I can see nothing more then a normal http call on the server side function. So do you have any idea how can we test with localhost? which is not possible to reach from the
Hi, Puneet,
Does your CAS installation use a custom login page? If so, check that the login
form includes the hidden "execution" field. Check the default casLoginPage.jsp
for reference on which JSP variable to use to populate the field's value.
Best regards,
--
Carlos M. Fernández
Sr. Enterpris
Hi,
Since CAS 4.0, resolvers are not longer mandatory. Your
deployerConfigContext.xml file looks good.
This kind of error (principal null in @Audit annotation) is generaly linked
to another error: don't you have something relevant in your error logs?
Thanks.
Best regards,
Jérôme LELEU
Founder
Hi,
Indeed, there is a fine tuning to "synchronize" the web session and SSO
session.
I would recommend to increase the idle timeout of the CAS server to
something greater than the web session, like one hour. This way, you would
reduce the likelihood to expire the CAS session while still maintaini
