Hi,
Since version 4 we made a modification to login flow in order to obtain
LastLogin attribute from databese.
Since last login is updated immideatly after login success, there is the
need to maintain previous login as attribute after that event.
We achieved that with an intermediate step in loginflow, which we would
like to have i future releases.
This is the modified login-flow:
<action-state id="generateServiceTicket">
<evaluate expression="generateServiceTicketAction" />
<transition on="success" to ="updateLastLogIn" />
<transition on="authenticationFailure"
to="handleAuthenticationFailure" />
<transition on="error" to="generateLoginTicket" />
<transition on="gateway" to="gatewayServicesManagementCheck" />
</action-state>
<action-state id="updateLastLogIn">
<evaluate expression="util.lastLogin(flowScope.credential)" />
<transition on="success" to="warn" />
</action-state>
--
- 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/CAMY5mieBJ_KAiCdH8hEoCRMD-QPzYV%2BTEHcQ6On%2BUb9jvnhybQ%40mail.gmail.com.
