[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 frontend login mechanism have become unreliable if the service do not sure the same domain. I think either use some custom login for logout, or use backend logout is needed if you need cross domain logout (e.g. CAS in www.example1.com, service in www.example2.com). Cheers! - Andy On Tuesday, 25 May 2021 at 01:29:11 UTC+8 john.b...@keap.com wrote: > > 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 > authenticated against. Is this a limitation of the Front Channel Logout > feature or do I have something configured improperly? > > Thanks, > > John > -- - 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 cas-user+unsubscr...@apereo.org. To view this discussion on the web visit https://groups.google.com/a/apereo.org/d/msgid/cas-user/b6eb93b7-71e2-493c-90b2-d5b4a50aca47n%40apereo.org.
[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 *gradlew.bat clean build *tasks and I get following message. > How do I resolve this? > > > Task :api:cas-server-core-api-configuration-model:checkstyleMain > [ant:checkstyle] [ERROR] > C:\Users\rm\Downloads\cas-6.2.3\api\cas-server-core-api-configuration-model\src\main\java\org\apereo\cas\configuration\CasConfigurationProperties.java:63: > > Configuration classes for tests must be marked with @TestConfiguration > [useTestConfiguration] > > > Task :api:cas-server-core-api-configuration-model:checkstyleMain FAILED > > FAILURE: Build failed with an exception. > > * What went wrong: > Execution failed for task > ':api:cas-server-core-api-configuration-model:checkstyleMain'. > > Checkstyle rule violations were found. See the report at: > file:///C:/Users/rm/Downloads/cas-6.2.3/api/cas-server-core-api-configuration-model/build/reports/checkstyle/main.html > Checkstyle files with violations: 1 > Checkstyle violations by severity: [error:1] > > > * Try: > Run with --stacktrace option to get the stack trace. Run with --info or > --debug option to get more log output. Run with --scan to get full insights. > > * Get more help at https://help.gradle.org > > Deprecated Gradle features were used in this build, making it incompatible > with Gradle 7.0. > Use '--warning-mode all' to show the individual deprecation warnings. > See > https://docs.gradle.org/6.6.1/userguide/command_line_interface.html#sec:command_line_warnings > > BUILD FAILED in 3m 39s > 47 actionable tasks: 34 executed, 13 up-to-date > > -- - 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 cas-user+unsubscr...@apereo.org. To view this discussion on the web visit https://groups.google.com/a/apereo.org/d/msgid/cas-user/9be62e47-5386-443b-afa0-b486eb058e86n%40apereo.org.
[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 authenticated against. Is this a limitation of the Front Channel Logout feature or do I have something configured improperly? Thanks, John -- - 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 cas-user+unsubscr...@apereo.org. To view this discussion on the web visit https://groups.google.com/a/apereo.org/d/msgid/cas-user/027aec62-07de-4a9b-a99a-769452da698cn%40apereo.org.
[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 the authentication request at org.apereo.cas.support.saml.web.idp.profile.AbstractSamlIdPProfileHandlerController.retrieveSamlAuthenticationRequestFromHttpRequest(AbstractSamlIdPProfileHandlerController.java:155) at org.apereo.cas.support.saml.web.idp.profile.sso.SSOSamlIdPProfileCallbackHandlerController.handleCallbackProfileRequest(SSOSamlIdPProfileCallbackHandlerController.java:87) at jdk.internal.reflect.GeneratedMethodAccessor478.invoke(Unknown Source) at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.base/java.lang.reflect.Method.invoke(Method.java:566) at org.springframework.util.ReflectionUtils.invokeMethod(ReflectionUtils.java:282) at org.springframework.cloud.context.scope.GenericScope$LockedScopedProxyFactoryBean.invoke(GenericScope.java:499) at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:186) at org.springframework.aop.framework.CglibAopProxy$CglibMethodInvocation.proceed(CglibAopProxy.java:749) at org.springframework.aop.framework.CglibAopProxy$DynamicAdvisedInterceptor.intercept(CglibAopProxy.java:691) at org.apereo.cas.support.saml.web.idp.profile.sso.SSOSamlIdPProfileCallbackHandlerController$$EnhancerBySpringCGLIB$$9408f46e.handleCallbackProfileRequest(generated) at jdk.internal.reflect.GeneratedMethodAccessor478.invoke(Unknown Source) at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.base/java.lang.reflect.Method.invoke(Method.java:566) at org.springframework.web.method.support.InvocableHandlerMethod.doInvoke(InvocableHandlerMethod.java:190) at org.springframework.web.method.support.InvocableHandlerMethod.invokeForRequest(InvocableHandlerMethod.java:138) at org.springframework.web.servlet.mvc.method.annotation.ServletInvocableHandlerMethod.invokeAndHandle(ServletInvocableHandlerMethod.java:105) at org.springframework.web.servlet.mvc.method.annotation.RequestMappingHandlerAdapter.invokeHandlerMethod(RequestMappingHandlerAdapter.java:878) at org.springframework.web.servlet.mvc.method.annotation.RequestMappingHandlerAdapter.handleInternal(RequestMappingHandlerAdapter.java:792) at org.springframework.web.servlet.mvc.method.AbstractHandlerMethodAdapter.handle(AbstractHandlerMethodAdapter.java:87) at org.springframework.web.servlet.DispatcherServlet.doDispatch(DispatcherServlet.java:1040) at org.springframework.web.servlet.DispatcherServlet.doService(DispatcherServlet.java:943) at org.springframework.web.servlet.FrameworkServlet.processRequest(FrameworkServlet.java:1006) at org.springframework.web.servlet.FrameworkServlet.doGet(FrameworkServlet.java:898) at javax.servlet.http.HttpServlet.service(HttpServlet.java:645) at org.springframework.web.servlet.FrameworkServlet.service(FrameworkServlet.java:883) at javax.servlet.http.HttpServlet.service(HttpServlet.java:750) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:227) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:162) at org.apereo.cas.web.support.AuthenticationCredentialsThreadLocalBinderClearingFilter.doFilter(AuthenticationCredentialsThreadLocalBinderClearingFilter.java:28) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:189) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:162) at org.apereo.cas.web.support.filters.RequestParameterPolicyEnforcementFilter.doFilter(RequestParameterPolicyEnforcementFilter.java:401) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:189) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:162) at org.apereo.cas.web.support.filters.ResponseHeadersEnforcementFilter.doFilter(ResponseHeadersEnforcementFilter.java:200) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:189) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:162) at org.apereo.cas.web.support.filters.AddResponseHeadersFilter.doFilter(AddResponseHeadersFilter.java:64) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:189) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:162) at org.springframework.security.web.FilterChainProxy.doFilterInternal(FilterChainProxy.java:204) at org.springframework.security.web.FilterChainProxy.doFilter(FilterChainProxy.java:183) at
[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: 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 cas-user+unsubscr...@apereo.org. To view this discussion on the web visit https://groups.google.com/a/apereo.org/d/msgid/cas-user/6cb36a8b-9fa2-4e40-9322-81bb155cb651n%40apereo.org.
