Re: [cas-user] Prevent CAS from overwriting the currently logged in user

Hi Ray, in an SSO scenario it is highly unlikely that a user would want to log on to services with different credentials. The same applies to the SLO scenario. Our customers and users think that the standard behaviour of CAS is a bug since SSO and SLO don't work as expected. (An existing

[cas-user] Changing LPPE Behavior

Is there a way to change the ldap password policy, for example, what I would like to do, When Must Change Password or Password Expired detected, allow the login instead of blocking, grant service ticket/tgt , as if no errors occurred so that I can redirect the user to our password management

[cas-user] Auto-Reload of Properties File Not Working

According to the documentation , the CAS properties files should auto-reload when a change is detected. I am not seeing that work in practice; changes to properties only take effect when I restart CAS. Is

Re: [cas-user] Prevent CAS from overwriting the currently logged in user

David, Paul, What if a user has a legitimate need to login to more than one service with differing credentials (maybe user has only one browser, does not know about private window, etc.)? What if user wanted to log out of first tab after a short time without triggering SLO in the other tab?

Re: [cas-user] CAS 6.1.4 - Unable to resolve Duo and Hazelcast dependencies

Thanks for the fast reply! They URL you sent was added to the build.gradle and resolved the Duo issue. Unfortunately, the build is still failing on the Hazelcast dependency. -Bryan On Mon, Feb 24, 2020 at 9:34 AM Jérôme LELEU wrote: > Hi, > > You need to add the Unicon repository: >

Re: [cas-user] Prevent CAS from overwriting the currently logged in user

Paul, When the second tab is loaded, there is no session cookie. The browser sends the form as it was loaded, not with new behaviour from another tab. (There is a hidden form field, execution, used to identify the log in attempt.) This is an interesting scenario. Perhaps it would be handy to

Re: [cas-user] CAS 6.1.4 - Unable to resolve Duo and Hazelcast dependencies

Hi, You need to add the Unicon repository: https://github.com/apereo/cas/blob/master/gradle/maven.gradle#L197 Thanks. Best regards, Jérôme Le lun. 24 févr. 2020 à 17:14, Bryan Wooten a écrit : > Following the instructions here: > > >

[cas-user] CAS 6.1.4 - Unable to resolve Duo and Hazelcast dependencies

Following the instructions here: https://apereo.github.io/2019/01/07/cas61-gettingstarted-overlay/#dependencies We are trying to add dependencies for Hazelcast and Duo by adding to the build.gradle file: compile "org.apereo.cas:cas-server-support-duo:${casServerVersion}" compile

Re: [cas-user] Prevent CAS from overwriting the currently logged in user

Wow David, awesome! Thanks a lot. That saves me a lot of time and headaches for sure. As you, I also wonder why this is the default behavior of CAS. After reading your linked thread I am even more worried as I wasn't aware of the logout consequences (only one of the two SSO sessions is

Re: [cas-user] Prevent CAS from overwriting the currently logged in user

And the code of TicketGrantingTicketCheckActionForSubmit.doExecute: final String tgtId = WebUtils.getTicketGrantingTicketId(requestContext); if (StringUtils.isBlank(tgtId)) { return new Event(this, CasWebflowConstants.TRANSITION_ID_TICKET_GRANTING_TICKET_NOT_EXISTS); } try { final

Re: [cas-user] Prevent CAS from overwriting the currently logged in user

Hi Paul, we had the same issue and solved it by changing the flow see https://groups.google.com/a/apereo.org/forum/#!msg/cas-user/Jjx3mm-kkhE/FzO5MsF9EAAJ in 6.1.x: final Flow flow = super.getLoginFlow(); //change the transition target of STATE_ID_VIEW_LOGIN_FORM from