Hi,
I developed a AutoLogin component to authenticate with our CAS
server. It is basically like the integrated CASAutoLogin, but with
some special twists to comply with our needs. It would work like
intended, but the order in which the Portal calls the different
AutoLogin components alters the request.
Our component gets called always after the default CASAutoLogin.
CASAutoLogin fails (which is fine) and calls the doHandleException
method, which contains following code:
HttpSession session = request.getSession();
if (e instanceof NoSuchUserException) {
session.removeAttribute(CASWebKeys.CAS_LOGIN);
session.setAttribute(
CASWebKeys.CAS_NO_SUCH_USER_EXCEPTION, Boolean.TRUE);
}
The method removes the login attribute which is crucial for my
AutoLogin component.
Is there a way to change the excecution order or a other way to
resolve this?
Thank you!
