[cas-user] Re: CAS Logout Redirect with Front Channel Logout

Hi John, It will use Ajax for frontend call, see this: https://github.com/apereo/cas/blob/master/support/cas-server-support-thymeleaf/src/main/resources/templates/logout/casPropagateLogoutView.html Note that, due to the recent 3rd party cookie blocking enforced in some of the popular browser,

[cas-user] Re: Configuration classes for tests must be marked with @TestConfiguration

Did you find a solution to this? I have the exact same problem. Excluding tests with gradlew -x test doesn't work. On Monday, October 12, 2020 at 8:44:29 PM UTC-6 RM2020 wrote: > Hi, I am using following https://github.com/apereo/cas/releases/tag/v6.2.3 > release to > do my first

[cas-user] CAS Logout Redirect with Front Channel Logout

Hi all, I maintain a CAS server, we have multiple services registered with different configurations. Some of the services are registered with Front Channel Logout. I have noticed that CAS will not redirect to the specified service on logout if one of the Front Channel Logout Services has been

[cas-user] waiting before giving attribute release consent

I have problem with cas configuration (or perhaps bug?) when attribute release consent is active and user waits for a few minutes on a consent screen before accepting it. The prolonged waiting causes following error: java.lang.IllegalArgumentException: SAML request could not be determined from

[cas-user] Azure authentication + LDAP attributes.

Hi, Some time ago, I setup CAS to delegate authentication to AZURE. It's working fine. Is there an option to release LDAP attributes after successful AZURE auth, just like normal CAS LDAP authentication? Thanks in advance. Bartek -- - Website: https://apereo.github.io/cas - Gitter Chatroom: