Re: [cas-user] attributeRepository.expireInMinutes, maximumCacheSize and merger is never taken into account

Thank you for your hints Manfredo, I finally managed to spot the problem: I was deploying CAS inside a Docker container which was not redeploying my modification on my application.yml file! When I modified this file inside my container, the cas.authn.attributeRepository.* attributes were

Re: [cas-user] attributeRepository.expireInMinutes, maximumCacheSize and merger is never taken into account

Here you see debug for expration set: ntingTicketImpl,prefix=TGT]]> 2018-02-07 17:49:37,322 DEBUG [org.apereo.cas.config.CasCoreTicketsSchedulingConfiguration] - 2018-02-07 17:49:37,673 DEBUG [org.apereo.cas.config.CasPersonDirectoryConfiguration] - 2018-02-07 17:49:37,679 DEBUG

Re: [cas-user] attributeRepository.expireInMinutes, maximumCacheSize and merger is never taken into account

Could you debug org.apereo.cas.configuration.CasConfigurationProperties where all properties are loaded. Also see from startup log which file properties are fetched Also set debug mode El miércoles, 7 de febrero de 2018, Anthony O. escribió: > I was just testing if this was

Re: [cas-user] attributeRepository.expireInMinutes, maximumCacheSize and merger is never taken into account

I was just testing if this was caused because I was using application.yml so I added the same values in cas.properties just to see (both are failing). I don't have other attribute sources I think... what properties would involve other attribute sources? The documentation is not clear about the

Re: [cas-user] attributeRepository.expireInMinutes, maximumCacheSize and merger is never taken into account

Do you have other attribute sources If multiple attribute repository sources are defined, they are added into a list and their results are cached and merged. El miércoles, 7 de febrero de 2018, Anthony O. escribió: > Thank you for this help Manfredo but as I said, I'm using

Re: [cas-user] attributeRepository.expireInMinutes, maximumCacheSize and merger is never taken into account

Why do you have application yml and cas properties El miércoles, 7 de febrero de 2018, Anthony O. escribió: > Hello, > > I'm trying to disable the cache of my cas.authn.attributeRepository in > order for the cas.authn.attributeRepository.jdbc to retrieve the > attributes each

Re: [cas-user] attributeRepository.expireInMinutes, maximumCacheSize and merger is never taken into account

Thank you for this help Manfredo but as I said, I'm using CAS v5.2.1 & 5.2.2 and this configuration parameter does not exist in this version : https://apereo.github.io/cas/5.2.x/installation/Configuration-Properties.html Moreover, the cas.authn.attributeRepository.merger is the same, and my