Re: [cas-user] CAS session management - Ticket Expiration Policies - CAS 6.5

2023-05-31 Thread Ray Bon
Niral, You will see in the logs that cas will issue a different TGT for each login; this means two different session == two different users (even if same username:password). In the same browser, open a new tab and access / log in to a different service. You can create fake services in your

RE: [cas-user] CAS session management - Ticket Expiration Policies - CAS 6.5

2023-05-31 Thread 'Niral Kunadia' via CAS Community
Ray, A you said you may have to get cas to issue a new ST[to a different application]. How can I add this for testing? I tested with two different browsers. Like login in chrome and did not touch it. I also login on edge and refreshing page every few mins, and I can see new service ticket

[cas-user] CAS 6.1+ logging attributes of Principal instead of just id - why?

2023-05-31 Thread Petr Bodnár
When on DEBUG, I have noticed that CAS logs are very long. One of the reasons is that commit [Clean up ToString methods](https://github.com/apereo/cas/commit/e2dc0b995316b6bc5a6523b2581a4aa7127aca5e) changed the `SimplePrincipal` class toString() method behavior: instead of returning just

Re: [cas-user] CAS session management - Ticket Expiration Policies - CAS 6.5

2023-05-31 Thread Ray Bon
Niral, A refresh of the cas page may not be enough. You may have to get cas to issue a new ST [to a different application]. The service does not have to be real, just added to the service registry. Use this type of url to get cas to go through the login process and issue a ST.

RE: [cas-user] CAS session management - Ticket Expiration Policies - CAS 6.5

2023-05-31 Thread 'Niral Kunadia' via CAS Community
Hello Ray, Thank you for reply. This is very useful. cas.ticket.tgt.primary.max-time-to-live-in-seconds=240 cas.ticket.tgt.primary.time-to-kill-in-seconds=180 These are the setting and for testing I am following these steps. I am login with cas credentials to web page, after login refresh

[cas-user] Problem update cas 6.6.7 to 6.6.8 with redis

2023-05-31 Thread Florent Vallée
Hello, I updated CAS from version 6.6.7 to 6.6.8. In Redis before tickets was of the form: CAS_TICKET:TGT-27121-mcqjW0C6kIt1w8IYM0sMMrhuLo4IIuxfaYy-bFAD4bQ59D9OXXyfJiHxx8Jr191A9KD9bdfLscRmL-hEzn-CW-xgjgHbofauT7HM1ARdPVqS7Syfv7VJwZx5-B40 MtvWSwBgpA-CAS:ttoto and now they are of the form:

Re: [cas-user] Re: MFA DUO for 6.6.7 errors

2023-05-31 Thread Andrey Nikolaev
Hi All I can not understand what's up here bypass = WHO: audit:unknown WHAT: {result=Service Access Granted, service= https://guacamole-01:6443/xtam/, requiredAttributes={}} ACTION: SERVICE_ACCESS_ENFORCEMENT_TRIGGERED APPLICATION: CAS

[cas-user] Problem update cas 6.6.7 to 6.6.8 with redis

2023-05-31 Thread lanf detroy
Hello, I updated CAS from version 6.6.7 to 6.6.8. In Redis before tickets was of the form: CAS_TICKET:TGT-27121-mcqjW0C6kIt1w8IYM0sMMrhuLo4IIuxfaYy-bFAD4bQ59D9OXXyfJiHxx8Jr191A9KD9bdfLscRmL-hEzn-CW-xgjgHbofauT7HM1ARdPVqS7Syfv7VJwZx5-B40 MtvWSwBgpA-CAS:ttoto and now they are of the form: