Where communities thrive

  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
Repo info
  • Sep 25 08:04

    mmoayyed on master

    Build performance tweaks (#5232… (compare)

  • Sep 25 08:04
    unfurl-links[bot] commented #5232
  • Sep 25 08:04
    welcome[bot] commented #5232
  • Sep 25 08:04
    mmoayyed closed #5232
  • Sep 25 02:24
    codecov[bot] commented #5232
  • Sep 25 02:16
    codecov[bot] commented #5232
  • Sep 25 02:14
    codecov[bot] commented #5232
  • Sep 25 02:09
    codecov[bot] commented #5232
  • Sep 25 02:06
    codecov[bot] commented #5232
  • Sep 25 02:02
    codecov[bot] commented #5232
  • Sep 25 02:00
    codecov[bot] commented #5232
  • Sep 25 01:59
    codecov[bot] commented #5232
  • Sep 25 01:55
    codecov[bot] commented #5232
  • Sep 25 01:54
    codecov[bot] commented #5232
  • Sep 25 01:51
    codecov[bot] commented #5232
  • Sep 25 01:48
    codecov[bot] commented #5232
  • Sep 25 01:46
    codecov[bot] commented #5232
  • Sep 25 01:45
    codecov[bot] commented #5232
  • Sep 25 01:42
    codecov[bot] commented #5232
  • Sep 25 01:38
    codecov[bot] commented #5232
Cardo Kambla
Discard my question. I was approaching the issue in a wrong way. I should have used /introspect request from the resource server to validate my access token. Also the library I was using is deprecated, so I am upgrading from it now.
Also I noticed with OIDC protocol, when I do the /introspect request. The expiration value of the token is not correct. The documentation states "Integer timestamp, measured in the number of seconds
since January 1 1970 UTC, indicating when this token will expire,
as defined in JWT" for the expiration time of the token. CAS has a default value of 28800 which does not correspond to that field correctly. It should start from 1576762337.
Cardo Kambla
the /introspect issuedAt and expiredAt response values need to be checked, when you leave the default values on, then spring security 5.2 resource server will throw the error "java.lang.IllegalArgumentException: expiresAt must be after issuedAt"
even though /introspect says the token is active, Spring Security 5.2 resource server sees a error when constructing the token object in java. It checks if issuedAt/expiredAt is null or not and when they are not null, it will check if expiredAt value is after issuedAt
Scott Williams
We're working on upgrading from 5.3 to 6.1 and seem to have hit the snag here (https://groups.google.com/a/apereo.org/forum/#!searchin/cas-user/trusted$20device%7Csort:date/cas-user/1tQbjF8NEtI/dff9nxqOAgAJ), where trusted devices no longer work for MFA. We're using mfa-gauth with mongodb for trusted devices. Is there any potential workaround? I'm afraid we might have to delay our deployment over it.
@mmoayyed Struggling trying to find a interruption point on source code in order to investigate. I tried the most obvious ones, like InitPasswordResetAction doExecute method but seems like the problem is way outside pm code. Can you point me to a good point to start debuging the webflow here?
Misagh Moayyed
@mikelasla If you don't mind, you could please summarize the problem for me? there have been too many posts and I have sort of lost track of the history here. What are you trying to do, and what's is causing a problem?
Hi, I'm running a CAS 5.3.14 on Tomcat behind Apache and I want to change my Apache configuration to do proxyHttp and not ProxyAJP beacuse I have timeout on AJP connection. I followed the blog post https://apereo.github.io/2018/01/05/cas-deployment-with-proxy/ but I still have the insecure notice
@millecentdix Ok I solved my problem by add secure="true" on the Tomcat connector
what is the latest updated stable cas version ?
when is the new updated version going to come up?
ERROR [org.apereo.cas.web.flow.resolver.impl.mfa.GlobalMultifactorAuthenticationPolicyEventResolver] [resolveInternal:GlobalMultifactorAuthenticationPolicyEventResolver.java:72] - <No multifactor authentication providers are available in the application context to handle [mfa-radius]>
Gary Windham

Hi all,

I'm testing CAS 6.1.2 in an external Jetty (9.4.24) container, and I've been running into an issue where CAS logs an error message like the following:

User limit of inotify instances reached or too many open files

Prior to a huge stack trace and the application shutting down.

I originally saw this issue when running the embedded Jetty container, then switched over to an external container to see if that would make any difference (it did not). I am running Jetty in a Docker container, and have increased the following sysctl parameters on the Docker host:

# sysctl -p
fs.inotify.max_user_watches = 560144
fs.inotify.max_user_instances = 512

I also have increased nofiles substantially, but that doesn't seem to have helped either.

Any ideas on where to begin looking to resolve this issue? I see CAS constantly logging messages like this: 2019-12-21 03:41:46,082 INFO [org.apereo.cas.util.io.PathWatcherService] - <Watching directory at [/etc/cas/config]>, which I assume to be related to the inotify issues.



Hi @mmoayyed, let me put some context

I'm trying to make Password Management work on 6.0.3 version against Active Directory. I also have another environment with OpenLDAP for testing. In both cases, auth works just fine, but PM doesn't.

Current behaviour is that PM correctly finds the user in the user directory and sends the token by mail.


But when I load the received URL, pswdrst urlParam seems to be ignored at all, regular login form gets loaded and no errors are shown in the logs, just this


This is the config for the OpenLDAP environment (replacing sensible values)

logging.config: file:/etc/cas/config/log4j2.xml
# https://apereo.github.io/cas/6.0.x/configuration/Configuration-Properties-Common.html#email-notifications
cas.authn.pm.autoLogin =true
cas.authn.pm.policyPattern =^(?=.*[a-z])[A-Za-z\\d]{4,}
cas.authn.pm.reset.mail.subject=Reset your password

@mmoayyed I also noticed this logs lines, so i pasted those propierties too

WARN [org.apereo.cas.util.cipher.BaseStringCipherExecutor] - <Generated encryption key [G3DuCmQupz-IC2TmAtl5dQrnz0EK0rQKOikWzzvM9Jg] of size [256] for [Password Reset Token]. The generated key MUST be added to CAS settings under setting [cas.authn.pm.reset.crypto.encryption.key].>

WARN [org.apereo.cas.util.cipher.BaseStringCipherExecutor] - <Generated signing key [lwrDVYc0vZ7Bl7FEqAnS7LbPPlMZ7xpaaz-d-1VRocox5praHqPC1hR1SNK8c8QtLaQqO933kReYoGVjpKNCYw] of size [512] for [Password Reset Token]. The generated key MUST be added to CAS settings under setting [cas.authn.pm.reset.crypto.signing.key].>

like that

Alberto Perillo
How can I add services to my CAS server?
I don't understood the docs
Alberto Perillo
I have a JSON file (that comes with CAS by default) that admit all https and imaps services to login with CAS, but when I try to login in CAS from an external service it returns "Application not allowed"
You need to specify a service in a specific JSON file. The service is "just" the name of the service or corresponding url of the systems that is allowed to talk to the CAS server.
Hi, I have a question regarding 6.* UI customization. In this post there's a mention of live-reload functionality being supported in 5.* via the build.sh script inside the overlay. As I understand that script is not a thing anymore having been replaced with gradle tasks. So my question is whether live-reload functionality is still present in 6.* and how I would go about getting it to work.
Cardo Kambla
I mentioned some time ago, that there is a problem with OAuth/OIDC /introspect request. When I get an access token from CAS and try to access some protected resource on my back-end, the /introspect request returns Unix Timestamp in seconds for issuedAt (iat) field (which is the expected behaviour) and expiresAt (exp) field has the configured value for accessTokens maxTimeToLiveInSeconds (default value 28800, which is not the expected behaviour, should also be unix timestamp). When Spring Security 5 tries to introspect the token, it sees that the expiredAt time is before the issued time and will throw a "IllegalArgumentException: expiresAt must be after issuedAt". When I checked the OAuth 2.0 token introspection standard, then it is stated that "exp" has to be of value "Integer timestamp, measured in the number of seconds since January 1 1970 UTC, indicating when this token will expire". TL:DR; OAuth/OIDC /introspect requests response value for expiresAt (exp) should be issuedAt + maxTimeToLiveInSeconds unix timestamp, currently it is just the maxTimeToLiveInSeconds value from CAS configuration.
This problem exists in version 6.2.0-SNAPSHOT and the resource server I am using for my back-end is Spring Security 5 OAuth2ResourceServer for introspection.
Cardo Kambla
I am gonna make a pull request on this but I still have not been able to test it yet, so it is gonna take some time for me until I get the pull request up.
I need to get to the site 'forgot password' directly, not from the login page. Is there any change to do that ?
Has anyone ran in to this ? Am on CAS v 6.1.2 and Java 11
Caused by: org.apache.velocity.exception.ResourceNotFoundException: Unable to find resource '/templates/saml2-post-binding.vm'
at org.apache.velocity.runtime.resource.ResourceManagerImpl.loadResource(ResourceManagerImpl.java:474)
Cardo Kambla
OIDC /revoke requests seems to get "javax.persistence.TransactionRequiredException: Executing an update/delete query" when it tries to delete a ticket. There is a transactional annotation present in that class. Update requests seem to be working because the tickets are added to the database.
audit config?
any audit database config example?
Cardo Kambla
I am using JPA ticket registry and a Postgres database, DDL is set to update.
Tables for ticket registry are created from startup and filled/selected when introspecting/asking access tokens.
Cardo Kambla
2020-01-02 13:55:13,622 ERROR [org.apereo.cas.oidc.web.controllers.token.OidcRevocationEndpointController] - <Executing an update/delete query>
javax.persistence.TransactionRequiredException: Executing an update/delete query
at org.hibernate.internal.AbstractSharedSessionContract.checkTransactionNeededForUpdateOperation(AbstractSharedSessionContract.java:409) ~[hibernate-core-5.4.10.Final.jar!/:5.4.10.Final]
at org.hibernate.query.internal.AbstractProducedQuery.executeUpdate(AbstractProducedQuery.java:1601) ~[hibernate-core-5.4.10.Final.jar!/:5.4.10.Final]
at jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method) ~[?:?]
at jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) ~[?:?]
at jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) ~[?:?]
at java.lang.reflect.Method.invoke(Method.java:566) ~[?:?]
at org.springframework.orm.jpa.SharedEntityManagerCreator$DeferredQueryInvocationHandler.invoke(SharedEntityManagerCreator.java:409) ~[spring-orm-5.2.2.RELEASE.jar!/:5.2.2.RELEASE]
at com.sun.proxy.$Proxy307.executeUpdate(Unknown Source) ~[?:?]
at org.apereo.cas.ticket.registry.JpaTicketRegistry.deleteSingleTicket(JpaTicketRegistry.java:209) ~[cas-server-support-jpa-ticket-registry-6.2.0-SNAPSHOT.jar!/:6.2.0-SNAPSHOT]
at org.apereo.cas.ticket.registry.AbstractTicketRegistry.deleteTicket(AbstractTicketRegistry.java:120) ~[cas-server-core-tickets-api-6.2.0-SNAPSHOT.jar!/:6.2.0-SNAPSHOT]
at org.apereo.cas.ticket.registry.AbstractTicketRegistry.deleteTicket(AbstractTicketRegistry.java:103) ~[cas-server-core-tickets-api-6.2.0-SNAPSHOT.jar!/:6.2.0-SNAPSHOT]
at org.apereo.cas.ticket.registry.AbstractTicketRegistryFastClassBySpringCGLIBFastClassBySpringCGLIBd3c67a11.invoke(<generated>) ~[cas-server-core-tickets-api-6.2.0-SNAPSHOT.jar!/:6.2.0-SNAPSHOT]
at org.springframework.cglib.proxy.MethodProxy.invoke(MethodProxy.java:218) ~[spring-core-5.2.2.RELEASE.jar!/:5.2.2.RELEASE]
at org.springframework.aop.framework.CglibAopProxy$DynamicAdvisedInterceptor.intercept(CglibAopProxy.java:685) ~[spring-aop-5.2.2.RELEASE.jar!/:5.2.2.RELEASE]
at org.apereo.cas.ticket.registry.JpaTicketRegistryEnhancerBySpringCGLIBEnhancerBySpringCGLIBe04acf1c.deleteTicket(<generated>) ~[cas-server-support-jpa-ticket-registry-6.2.0-SNAPSHOT.jar!/:6.2.0-SNAPSHOT]
at jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method) ~[?:?]
at jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) ~[?:?]
at jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) ~[?:?]
at java.lang.reflect.Method.invoke(Method.java:566) ~[?:?]
at org.springframework.util.ReflectionUtils.invokeMethod(ReflectionUtils.java:282) ~[spring-core-5.2.2.RELEASE.jar!/:5.2.2.RELEASE]
at org.springframework.cloud.context.scope.GenericScope$LockedScopedProxyFactoryBean.invoke(GenericScope.java:499) ~[spring-cloud-context-2.2.1.RELEASE.jar!/:2.2.1.RELEASE]
at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:186) ~[spring-aop-5.2.2.RELEASE.jar!/:5.2.2.RELEASE]
at org.springframework.aop.framework.JdkDynamicAopProxy.invoke(JdkDynamicAopProxy.java:212) ~[spring-aop-5.2.2.RELEASE.jar!/:5.2.2.RELEASE]
at com.sun.proxy.$Proxy163.deleteTicket(Unknown Source) ~[?:?]
at org.apereo.cas.oidc.web.controllers.token.OidcRevocationEndpointController.handleRequestInternal(OidcRevocationEndpointController.java:68) ~[cas-server-support-oidc-core-api-6.2.0-SNAPSHOT.jar!/:6.2.0-SNAPSHOT]
Alberto Perillo
@infinity202 thanks for the docs. but I have CAS 6.1 (not 5.1) and it sems that it isn't work in the same way
And I don't understand this
"Support is enabled by adding the following module into the Maven overlay:"
In which file I have to add that?
Cardo Kambla
maven configuration goes into pom.xml file
CAS uses gradle afaik, you should be able to add the same dependency in gradle also
Cardo Kambla
@perillo3ro if you want to add a service from JSON (with overlay method):
0.1 Add dependency to gradle file under dependencies -> implementation "org.apereo.cas:cas-server-support-json-service-registry:${project.'cas.version'}"
0.2 Clean build CAS
  1. Create a json file
  2. Add data to that json file (from documentation)
  3. Add/replace that json file to your /etc/cas/services folder ( gradlew copyCasConfiguration does not copy it )
  4. In your cas.properties file check that cas.serviceRegistry.json.location is pointing toward that folder where the json is ( in my case file:/etc/cas/services)
  5. Also in cas.properties put cas.serviceRegistry.initFromJson=true .
  6. gradlew copyCasConfiguration
  7. run CAS
Alberto Perillo
Thanks, i'll try this
@tanghaojie cas.ticket.registry.jpa.user=portaldb_user
cas.ticket.registry.jpa.healthQuery=SELECT 1
Scott Williams
Is there any way to limit the users that are evaluated by risk based adaptive triggering? It ended up causing massive Mongo database load when enabled that effectively DOS'd the CAS service (6.1)
Philipp Berger

Hi all, we are currently using CAS 5.3.14 and facing the issue that our implementation of org.apereo.services.persondir.IPersonAttributeDao is called on every creation of a ProxyGrantingTicket. For me it looks like org.apereo.cas.audit.AuditableExecution.execute(AuditableContext) leads to org.apereo.cas.authentication.principal.cache.AbstractPrincipalAttributesRepository.retrievePersonAttributesToPrincipalAttributes(String) which is called for any service url. Is this the intended behavior?

Any comments on that? We are still facing the issue...

Alberto Perillo
@CardoKambla I put that in build.gradle and get this error

FAILURE: Build failed with an exception.

  • Where:
    Build file '/root/cas-6.1.x/build.gradle' line: 46

  • What went wrong:
    A problem occurred evaluating root project 'cas-server'.

    Could not get unknown property 'cas.version' for root project 'cas-server' of type org.gradle.api.Project.