Re: [cas-user] CAS 6 Attribute Release

2020-06-01 Thread Bryan Wooten
I added those log settings... We also tried changing our gradle.properties from SNAPSHOT to RC5 and that just broke the Duo login flow... I added this to cas.properties: #Attribute Release cas.authn.authenticationAttributeRelease.enabled=true And I also change the JSON service registry

Re: [cas-user] cas.ticket.tgt.timeout.maxTimeToLiveInSeconds and Memcache ticket experation policy

2020-06-01 Thread John Bond
Hi Ray, Thanks for the response however ... On Mon, Jun 1, 2020 at 6:16 PM Ray Bon wrote: > John, > > > https://apereo.github.io/cas/6.1.x/ticketing/Configuring-Ticket-Expiration-Policy.html > > timeout.maxTimeToLive... is a hard timeout. The other is a 'must be used > within this time' to be

[cas-user] CAS 6.1.6 inotify instances skyrocketing with Groovy files in SAML service.

2020-06-01 Thread William Jojo
Been running 6.1.6 for about 2 weeks. No issues - until I added SAML support. This morning I noticed CAS no longer working. Checked log and found: >From log: 2020-06-01 09:05:32,086 INFO [org.apereo.cas.util.io.PathWatcherService] - <*Watching directory at [/etc/cas/saml]*> 2020-06-01

[cas-user] cas.ticket.tgt.timeout.maxTimeToLiveInSeconds and Memcache ticket experation policy

2020-06-01 Thread John Bond
Hello All, In out config we set both cas.ticket.tgt.timeout.maxTimeToLiveInSeconds and cas.ticket.tgt.maxTimeToLiveInSeconds to the same value believing theses where the same and made a note to validate this with this group[1]. That later step never happened and the config remained. however

Re: [cas-user] CAS 6 Attribute Release

2020-06-01 Thread Ray Bon
Bryan, Maybe these loggers can help. Ray On Mon, 2020-06-01 at 08:34 -0600, Bryan Wooten wrote: We are doing a POC with CAS 6. We are building using the war overlay. Are build is from the CAS 6 Master branch. I have a simple Java client app configured for

Re: [cas-user] cas.ticket.tgt.timeout.maxTimeToLiveInSeconds and Memcache ticket experation policy

2020-06-01 Thread Ray Bon
John, https://apereo.github.io/cas/6.1.x/ticketing/Configuring-Ticket-Expiration-Policy.html timeout.maxTimeToLive... is a hard timeout. The other is a 'must be used within this time' to be valid. If the TGT is used within this window, the validity will extend by that time up to

[cas-user] CAS 6 Attribute Release

2020-06-01 Thread Bryan Wooten
We are doing a POC with CAS 6. We are building using the war overlay. Are build is from the CAS 6 Master branch. I have a simple Java client app configured for SAML1.1. This app is running on the same Tomcat as CAS 6 itself. This is its JSON service registry entry: { "@class" :

[cas-user] how to include authenticated user's roles in JWT?

2020-06-01 Thread dg
hello, i have configured cas as oauth2 server. after successfull login, it returns JWT, but roles filed in jwt is always empty []. how can fetch and put authenticated user's role in JWT? thanks for helps. -- - Website: https://apereo.github.io/cas - Gitter Chatroom:

Re: [cas-user] cas.ticket.tgt.timeout.maxTimeToLiveInSeconds and Memcache ticket experation policy

2020-06-01 Thread Ray Bon
John, Timeout has higher priority than Default. timeout.maxTimeToLiveInSeconds is a more general approach (an application like an webmail client, that hits cas every 10m when it checks for new mail, will keep the TGT alive while the tab is open). The two settings in Default,