Hi. I have problem with my cas configuration. I have 2 authentication sources named DOMAIN and EXTERNAL. I Also have service definition that require user to be logged in through DOMAIN authn
{
"@class" : "org.apereo.cas.services.OidcRegisteredService",
"clientId": "myclientid",
"clientSecret": "myclientsecret",
"serviceId" : "https?://(localhost|[0-9]+\\.[0-9]+\\.[0-9]+\\.[0-9]+).*",
"name": "oidc",
"id": 17,
"supportedGrantTypes" : ["java.util.HashSet", ["authorization_code", "refresh_token"]],
"encryptIdToken" : true,
"bypassApprovalPrompt" : true,
"accessStrategy" : {
"@class" : "org.apereo.cas.services.DefaultRegisteredServiceAccessStrategy",
"enabled" : true,
"ssoEnabled" : true
},
"authenticationPolicy" : {
"@class" : "org.apereo.cas.services.DefaultRegisteredServiceAuthenticationPolicy",
"requiredAuthenticationHandlers" : ["java.util.TreeSet", [ "DOMAIN" ]],
"excludedAuthenticationHandlers" : ["java.util.TreeSet", [ "EXTERNAL" ]],
"criteria": {
"@class" : "org.apereo.cas.services.AnyAuthenticationHandlerRegisteredServiceAuthenticationPolicyCriteria"
}
}
}If I attempt to sign in directly to this service providing DOMAIN credentials, then everything works fine.
But if I start by signing in with EXTERNAL credentials and already have cas session, and then I try to sign in to this service i keep getting loginForm. Even thought I provide correct credentials for DOMAIN it still returns UNSATISFIED_AUTHN_POLICY message. In CAS logs I can see that AuthenticationPolicy passes with "Authentication policy is satisfied having found at least one authentication transactions" message. I don't really know what is blocking the flow later.
I need to logout from cas and retry login to make it work again but I don't want to give up sso functionality.
I'm using CAS version 6.4.3.
I'll be thankful for any hints.
@mmoayyed there is requirement to upgrade log4j2 to 2.15.0
1 reply
My current version is 6.2.6, Docker mode deployment.
2 replies
can we add log4j2.formatMsgNoLookups=true to the cas properties file to mitigate the log4j vulnerability?
@lgwozniak
https://logging.apache.org/log4j/2.x/security.html create PR
@mmoayyed there is requirement to upgrade log4j2 to 2.15.0
https://logging.apache.org/log4j/2.x/security.html create PR
@mmoayyed there is requirement to upgrade log4j2 to 2.15.0
1 reply
Hi guys, I got this error while try to build cas overlay template. 😰
release version 11 not supportedMy Gradle info
------------------------------------------------------------
Gradle 7.3.1
------------------------------------------------------------
Build time: 2021-12-01 15:42:20 UTC
Revision: 2c62cec93e0b15a7d2cd68746f3348796d6d42bd
Kotlin: 1.5.31
Groovy: 3.0.9
Ant: Apache Ant(TM) version 1.10.11 compiled on July 10 2021
JVM: 11.0.12 (Red Hat, Inc. 11.0.12+7-LTS)
OS: Linux 4.14.256-197.484.amzn2.x86_64 amd64
can we add log4j2.formatMsgNoLookups=true to the cas properties file to mitigate the log4j vulnerability?
This is what the official patching guide seems to infer (https://apereo.github.io/2021/12/11/log4j-vuln/#patching)
As someone new to CAS, my question is: how do I know that the patch (java -Dlog4j2.formatMsgNoLookups=true -jar cas.war) was applied successfully?
2 replies
I've seen that updating to Spring Boot 2.0 is one way to fix this. My question is: can Cas 5.2.x run on Spring Boot 2.0 ?
Currently configured with Spring Boot 1.5.8.RELEASE
java.lang.reflect.InaccessibleObjectException: Unable to make public long com.sun.management.internal.OperatingSystemImpl.getOpenFileDescriptorCount() accessible: module jdk.management does not "opens com.sun.management.internal" to unnamed module
Also relevant: https://www.zdnet.com/article/second-log4j-vulnerability-found-apache-log4j-2-16-0-released/
2.15.0 might not be "enough."
Hello,
i have same error to @choidkdk , but i have docker-compose and i use cas-overlay-template/tree/6.3 .
this error happens when I use 'docker-compose build'.
I will not install openjdk because I am in a container .
thanks for your help
i have same error to @choidkdk , but i have docker-compose and i use cas-overlay-template/tree/6.3 .
this error happens when I use 'docker-compose build'.
I will not install openjdk because I am in a container .
thanks for your help
Building cas
Step 1/20 : FROM adoptopenjdk/openjdk11:alpine-slim AS overlay
---> 68d79b94d8b9
Step 2/20 : RUN mkdir -p cas-overlay
---> Using cache
---> 2fbf67e30ccc
Step 3/20 : COPY ./src cas-overlay/src/
---> 492ae4217531
Step 4/20 : COPY ./gradle/ cas-overlay/gradle/
---> d44ca8ef2c0e
Step 5/20 : COPY ./gradlew ./settings.gradle ./build.gradle ./gradle.properties /cas-overlay/
---> 6c0d5aaa1d06
Step 6/20 : RUN mkdir -p ~/.gradle && echo "org.gradle.daemon=false" >> ~/.gradle/gradle.properties && echo "org.gradle.configureondemand=true" >> ~/.gradle/gradle.properties && cd cas-overlay && chmod 750 ./gradlew && ./gradlew --version;
---> Running in 17e37e5f3ced
Downloading https://services.gradle.org/distributions/gradle-7.3.1-bin.zip
...........10%...........20%...........30%...........40%...........50%...........60%...........70%...........80%...........90%...........100%
Welcome to Gradle 7.3.1!
Here are the highlights of this release:
- Easily declare new test suites in Java projects
- Support for Java 17
- Support for Scala 3
For more details see https://docs.gradle.org/7.3.1/release-notes.html
------------------------------------------------------------
Gradle 7.3.1
------------------------------------------------------------
Build time: 2021-12-01 15:42:20 UTC
Revision: 2c62cec93e0b15a7d2cd68746f3348796d6d42bd
Kotlin: 1.5.31
Groovy: 3.0.9
Ant: Apache Ant(TM) version 1.10.11 compiled on July 10 2021
JVM: 11.0.8 (AdoptOpenJDK 11.0.8+10)
OS: Linux 4.18.0-348.2.1.el8_5.x86_64 amd64
Removing intermediate container 17e37e5f3ced
---> f0df1a5519e8
Step 7/20 : RUN cd cas-overlay && ./gradlew clean build --parallel --no-daemon;
---> Running in 89755da20e71
To honour the JVM settings for this build a single-use Daemon process will be forked. See https://docs.gradle.org/7.3.1/userguide/gradle_daemon.html#sec:disabling_the_daemon.
Daemon will be stopped at the end of the build
Configuration on demand is an incubating feature.
> Task :clean
> Task :extractCasBootWarOverlay
> Task :bootBuildInfo
> Task :generateMainEffectiveLombokConfig1
> Task :checkLombokConfig
> Task :compileJava FAILED
Deprecated Gradle features were used in this build, making it incompatible with Gradle 8.0.
You can use '--warning-mode all' to show the individual deprecation warnings and determine if they come from your own scripts or plugins.
See https://docs.gradle.org/7.3.1/userguide/command_line_interface.html#sec:command_line_warnings
6 actionable tasks: 6 executed
FAILURE: Build failed with an exception.
* What went wrong:
Execution failed for task ':compileJava'.
> error: release version 11 not supported
* 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
BUILD FAILED in 53s
hello!, we update from 6.4.0 to 6.4.4 due to log4shell cas config working well but we have this error when return fron azureAD delegated auth, any thoughs?
java.lang.IllegalAccessError: class org.pac4j.oidc.profile.creator.OidcProfileCreator tried to access protected method 'void com.nimbusds.oauth2.sdk.ProtectedResourceRequest.<init>(java.net.URI, com.nimbusds.oauth2.sdk.token.AccessToken)' (org.pac4j.oidc.profile.creator.OidcProfileCreator and com.nimbusds.oauth2.sdk.ProtectedResourceRequest are in unnamed module of loader org.springframework.boot.loader.LaunchedURLClassLoader @277050dc)
at org.pac4j.oidc.profile.creator.OidcProfileCreator.create(OidcProfileCreator.java:94)
at org.pac4j.core.client.BaseClient.retrieveUserProfile(BaseClient.java:126)
at org.pac4j.core.client.BaseClient.getUserProfile(BaseClient.java:105)
at org.apereo.cas.support.pac4j.authentication.handler.support.DelegatedClientAuthenticationHandler.doAuthentication(DelegatedClientAuthenticationHandler.java:78)
at org.apereo.cas.authentication.handler.support.AbstractPreAndPostProcessingAuthenticationHandler.authenticate(AbstractPreAndPostProcessingAuthenticationHandler.java:44)
at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
Hello I'm using CAS 6.4.2 (log4j 2.14.1) i rebuilding the project and i add these lines
-- add to build.gradle dependencies section
implementation "org.apache.logging.log4j:log4j-api:2.16.0"
implementation "org.apache.logging.log4j:log4j-core:2.16.0"
implementation "org.apache.logging.log4j:log4j-jcl:2.16.0"
implementation "org.apache.logging.log4j:log4j-jul:2.16.0"
implementation "org.apache.logging.log4j:log4j-web:2.16.0"
implementation "org.apache.logging.log4j:log4j-slf4j18-impl:2.16.0"-- add to the end of build.gradle
bootWar {
entryCompression = ZipEntryCompression.STORED
overlays {
cas {
from "org.apereo.cas:cas-server-webapp${project.appServer}:${casServerVersion}@war"
provided = false
excludes = ["WEB-INF/lib/log4j2.12..jar","WEB-INF/lib/log4j2.14..jar"]
}
}
}
the buid is OK successfull so i want to know if my CAS use log4j2.16 now and how to verify it????
Should only contain 2.16.0
it's ok i juste want to copy the new cas.war
Hi, We are currently using 6.3.2 version of CAS. To fix the log4j Vulnerability, we have upgraded the cas version to 6.3.7.4. After updating the version, we are facing the below issue
> Could not resolve all files for configuration ':casBootWarOverlay'.
> Could not resolve org.apereo.cas:cas-server-webapp-tomcat:6.3.7.4.
Required by:
project :
> Cannot choose between the following variants of org.apereo.cas:cas-server-webapp-tomcat:6.3.7.4:
- master
- samplessources
All of them match the consumer attributes:
- Variant 'master' capability org.apereo.cas:cas-server-webapp-tomcat:6.3.7.4:
- Unmatched attributes:
- Provides org.gradle.status 'release' but the consumer didn't ask for it
- Provides org.gradle.usage 'java-runtime' but the consumer didn't ask for it
- Variant 'samplessources' capability org.apereo.cas:cas-server-webapp-tomcat:6.3.7.4:
- Unmatched attributes:
- Provides org.gradle.category 'documentation' but the consumer didn't ask for it
- Provides org.gradle.docstype 'samplessources' but the consumer didn't ask for it
- Provides org.gradle.status 'release' but the consumer didn't ask for itAs per the gradle documentation, looks like there are multiple variants. Can you please help me to resolve this issue?
1 reply
(working with the newest CAS release)
There seems to be a possibility to run the war as a linux service: https://apereo.github.io/cas/6.4.x/installation/Configuring-Deployment-System-Service.html
But trying to find or build this WAR results in a bunch of files that want to create a docker machine on my virtual server and I don't want that.
But trying to find or build this WAR results in a bunch of files that want to create a docker machine on my virtual server and I don't want that.
Hi While upgrading the cas from 6.1.7 to 6.4.4.2 we are seeing a issue where oidc 2022-01-10 22:30:38,625 TRACE [org.apereo.cas.oidc.util.OidcRequestSupport] - <Configured issuer [http://example.com] defined does not match the request issuer [http://local:8080/cas/oidc]>
2022-01-10 22:30:38,625 WARN [org.apereo.cas.oidc.web.controllers.discovery.OidcWellKnownEndpointController] - <Unable to accept request; issuer for endpoint [.well-known] is invalid>
Even on local we notice if no oidc config is provide it default to 8080 and not sue the tomcat port or the cas config.
2022-01-10 22:30:38,625 WARN [org.apereo.cas.oidc.web.controllers.discovery.OidcWellKnownEndpointController] - <Unable to accept request; issuer for endpoint [.well-known] is invalid>
Even on local we notice if no oidc config is provide it default to 8080 and not sue the tomcat port or the cas config.
whenever authentication flow fails due to invalid credentials, CAS returns HTTP status 401 with login page. Is there any way by which we can return HTTP status 200 for such cases?Because HTTP status 401 caused a monitoring alarm, I had to find a way to change it to HTTP status 200.
did anyone have issues?
Hey! Nobody noticed that the last version of CAS client for Java, its build for Java 8, but have a dependency to JAXB 2.3.1 that its for Java 9 ?
Also, the READMED should clarify what version of Java it's being supported.
Anyone could annotate this on the issues system that you are using ? I would liked to do this, but I don't see that I could done on GitHub repo, and I don't see a Jira o r Mantis to do it.
i have an issue with CAS 6.4.4, when i login into saml sp, cas will release all auth attributes + allowed, why ?
I put
attributeReleasePolicy: !<org.apereo.cas.services.ReturnMappedAttributeReleasePolicy>
allowedAttributes: !<java.util.TreeMap>
mail: !<java.util.ArrayList>
- "mail"
principalAttributesRepository: !<org.apereo.cas.authentication.principal.DefaultPrincipalAttributesRepository>
attributeRepositoryIds: !<java.util.HashSet>
- "*"
consentPolicy: !<org.apereo.cas.services.consent.DefaultRegisteredServiceConsentPolicy>
status: "FALSE"
excludeDefaultAttributes: true
authorizedToReleaseAuthenticationAttributes: false
Hi
I am in the process of setting up two CAS servers with the same DNS rrcas.mydomain.com and the IP addresses are 10.10.10.10 and 10.10.10.11. Each CAS marks in isolation but if I activate the NGINX for both I have a ticket issue I would like to know how to configure Hazelcast (or another) to respond to the ticket issue.
I am in the process of setting up two CAS servers with the same DNS rrcas.mydomain.com and the IP addresses are 10.10.10.10 and 10.10.10.11. Each CAS marks in isolation but if I activate the NGINX for both I have a ticket issue I would like to know how to configure Hazelcast (or another) to respond to the ticket issue.
if someone has already configure hazelcast or High Avalaibility CAS cluster please i need some help
Hey guys, i got a strange problem trying to activate acceptable-usage-policy with jdbc in 6.3.7.4 - After LDAP User XXX logging in, they have to accept the policy. On "ACCEPT" they'll loop on this site. Logs showing no "aupAccepted"-Attribute but attribute with value "true" is written to database - even if there is no entry for the user. When working with enabled Caching for Attribute-Repository there will be a value "1" for aupAccepted but this looks like not or wrong converted to boolean, as aup is showing "NOT ACCEPTED. Anyone else with similar issue?!