Hi Yan,
As Ray correct pointed out the XML webflow defined is a basic starting
point, if search through the you find alot of class extending
Cas*Webflow*Configurer
this include the DefaultLoginWebflowConfigurer.
During our upgrade from I noticed the same issue that at times the service
parameter was going missing, but the page worked fine as long as I did NOT
do a refresh. From my investigation the service parameter is stored upon
entry into CAS and as long as the page is not force refresh from the user
without the service parameter then CAS should work fine.
During my investigation I found the following redirect,
<end-state id="redirectView" view="externalRedirect:#{requestScope.url}"/>
They redirect without the query parameters. There is also a redirectToLogin
as well.
<end-state id="redirectToLogin" view="externalRedirect:#{'login'}"/>
Given that you have started invalid credentials then its more than likely
going down the "<transition on="authenticationFailure"
to="handleAuthenticationFailure"/>" code and not even hitting your code.
Regards,
Colin
On Thursday, 7 February 2019 05:00:05 UTC+11, Yan Zhou wrote:
>
> Hi there,
>
> I extended CAS 5.3.4. The app. redirects to CAS login page with service
> parameter.
>
> When I type incorrect credential, I saw the invalid credential message,
> but I lost service parameter, the screen refreshes to have only the CAS url.
>
> What could be missing in my code?
>
> Thx!
>
--
- Website: https://apereo.github.io/cas
- Gitter Chatroom: https://gitter.im/apereo/cas
- List Guidelines: https://goo.gl/1VRrw7
- Contributions: https://goo.gl/mh7qDG
---
You received this message because you are subscribed to the Google Groups "CAS
Community" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To view this discussion on the web visit
https://groups.google.com/a/apereo.org/d/msgid/cas-user/90d3d5d5-e32f-4cdd-a817-083cea2d689f%40apereo.org.