Hi,
We are running v6.5.2 and turned on the Duo Universal Prompt without issues
back in January. But recently I noticed that the "public workstation"
checkbox doesn't seem to work.
Last time I noticed it working was when we upgraded to v6.5.2. Working to
debug this issue further. Has anyon
We've tested the Universal Prompt and Interrupt in v 6.5.2 without issues.
-ds
Dave Steiner, Rutgers University
On Tuesday, January 3, 2023 at 10:41:58 PM UTC-5 j-gar...@onu.edu wrote:
> For anyone else who finds this in the future:
> It looks like this bug has been corrected by ve
em to
downgrade to Lax?
thanks,
ds
Dave Steiner
Rutgers University
--
- 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 t
under 5 minutes so I think we're good but we just
want to make sure we're not missing something.
thanks,
ds
Dave Steiner
Rutgers University, IdM Architect
--
- Website: https://apereo.github.io/cas
- Gitter Chatroom: https://gitter.im/apereo/cas
- List Guidelines: https://goo.gl
So I was just doing the same thing... hopefully you've already figured this
out but
Hazelcast doesn't seem to like it when you change certain values while it's
running. So you can handle this two ways:
1. Bring down all servers using Hazelcast, make the changes and bring them
back up, or
Currently (v5.3) we have a locally added "getstatus" endpoint that the
LoadBalancers use to check if the server is up or not. We couldn't seem to
add this in v6 (not sure how long the developer tried). I remember we used
the status endpoint in v5 but that would take too long for the LB and it
We are currently upgrading from v5 to v6 and use JPA like you are. What we
are doing is to use the CAS5 endpoint /status/services/export to get a zip
file of all our Service entries (~1000-1500). We then need to make a minor
change to those and will be using the CAS6 endpoint
/actuator/regi
So we recently got v5.3.5 into Production and am using the /status endpoint
for our load balancer checks. But evidently that's taking too long for the
LB and it's saying that server is down. As far as I know, /status doesn't
do a whole lot but it's taking over 16 seconds under minimal load.
ds to kill the surrogate session and
> consider tickets expired.",
> "defaultValue" : 1800,
> "hints" : {
> "keyHints" : [ ],
> "keyProviders" : [ ],
> "valueHints" : [ ],
> "valueProvi
29:44,143 DEBUG
[org.apereo.cas.ticket.registry.HazelcastTicketRegistry] -
cas-2020-12-09-11-1.log:2020-12-09 11:29:44,147 DEBUG
[org.apereo.cas.ticket.registry.HazelcastTicketRegistry] -
On Tuesday, December 8, 2020 at 11:42:02 PM UTC-5 Dave Steiner wrote:
> Here's the debug logs I see when I have to reauthenticat
WARN
[org.apereo.cas.ticket.registry.AbstractTicketRegistry] -
2020-12-08 23:35:28,154 INFO
[org.apereo.inspektr.audit.support.Slf4jLoggingAuditTrailManager] -
On Friday, December 4, 2020 at 3:44:18 PM UTC-5 Dave Steiner wrote:
> The usual "expire when the browser is closed".
>
>
The usual "expire when the browser is closed".
On Wednesday, December 2, 2020 at 5:31:12 PM UTC-5 Ray Bon wrote:
> Dave,
>
> What is the expiry time on the TGC in your browser?
>
> Ray
>
> On Wed, 2020-12-02 at 14:25 -0800, Dave Steiner wrote:
>
> Notice: T
8 AM UTC-5 Priyambada Madala wrote:
> Hi Dave,
>
> Do you have any hazelcast config with time out . This can also result with
> tickets getting timed out .
>
> On Wednesday, December 2, 2020 at 1:36:02 AM UTC+5:30 Dave Steiner wrote:
>
>> We had started the upgrade a while
atest CAS v
> 6.x, as 5.x is EOL?
>
> Best,
> D.
>
> On Dec 1, 2020 at 13:10:26, Dave Steiner wrote:
>
>>
>> We are upgrading to v5.3.5 and I was just testing the TGT timeout. I am
>> using hazelcast and have the following settings:
&
We are upgrading to v5.3.5 and I was just testing the TGT timeout. I am
using hazelcast and have the following settings:
cas.ticket.tgt.maxTimeToLiveInSeconds=28800
cas.ticket.tgt.timeToKillInSeconds=28800
But I notice after an hour or so, that I have to re-authenticate. In the
logs, I'm see
15 matches
Mail list logo
