Hi Alex, I'd encourage you to look at the login-webflow.xml file. In there is where all the routing decisions are made related to the login process. It uses the Spring Webflow technology.
It sounds like you have multiple things to check for. You might look at the "realSubmit" action-state in the login-webflow.xml as an example, and reverse-engineer from there. The evaluation expression object (authenticationViaFormAction) is defined in the cas-servlet.xml file. That class might be overcomplicated for an example but it should give you an idea of how to branch in the login-webflow.xml. Good luck. John On 5/5/14, 7:02 PM, Alex Worker wrote: > Hi, > > Could please someone point me the proper way of implementation the > feature: > (CAS 3.5 + LDAP + JAVA/JSP) > > After user successfully logging to CAS > - show to client specific page (if it necessary ) > - or redirect to app (usual behavior) > > This might happens if client need to agree the terms of use, or > change password, etc... > > The JSP page + back logic is implemented, but I just replaced the > default success page > > casLoginGenericSuccessView.(class)=org.springframework.web.servlet.view.JstlView > casLoginGenericSuccessView.url=/myPage.jsp > > I need to force it work when service redirect to CAS to auth. > > Thank you for your comments/ideas/code examples > -- > 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 -- *John Gasper* IAM Consultant Unicon, Inc. -- 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
