[cas-user] Re: CAS 6.4 DelegatedAuthentication Loigout error

2024-04-26 Thread Pablo Vidaurri
Thank you for the link. I have reviewed, made slight modification to use AzureAdProfile.class instead of OidcProfile.class. So far looking much better. I appreciate the assist! -psv On Thursday, April 25, 2024 at 6:08:58 AM UTC-5 flo13270 wrote: > Hello, > Yes, I solved the problem by modif

[cas-user] Re: CAS 6.4 DelegatedAuthentication Loigout error

2024-04-25 Thread flo13270
Hello, Yes, I solved the problem by modifying the file support/cas-server-support-pac4j-core-clients/src/main/java/org/apereo/cas/support/pac4j/serialization/DelegatedClientJacksonModule.java https://github.com/apereo/cas/pull/5626/files Hope it works for you too Le jeudi 18 avril 2024 à 06:43:4

[cas-user] Re: CAS 6.4 DelegatedAuthentication Loigout error

2024-04-17 Thread Pablo Vidaurri
Did you get around this issue. Facing the same problem with Azure AD delegation but I'm using Postgres not Mongo. Looks like perhaps when user profile is being saved to the session it may end up getting encrypted. On the saveAll, I see user profile in logs as plain text. But when reading user p

[cas-user] Re: CAS 6.4 DelegatedAuthentication Loigout error

2023-03-30 Thread Juan Manuel Díaz Nevado
hi, nope, we continue using redis for tickets registry and move to cas 6.6 now, but not try again with mongo due to we are happy with redis performance. Cheers. El miércoles, 29 de marzo de 2023 a las 16:15:00 UTC+2, floria...@gmail.com escribió: > Hi, > We encounter a similar problem. > > M

[cas-user] Re: CAS 6.4 DelegatedAuthentication Loigout error

2023-03-29 Thread flo13270
Hi, We encounter a similar problem. Migration from CAS 5.3 (with Redis) to CAS 6.6 (with Mongo) broke the logout of users authenticated through OIDC. ("class java.lang.String cannot be cast to class org.pac4j.core.profile.UserProfile") Did you finally succeed in fixing it while still using Mong

[cas-user] Re: CAS 6.4 DelegatedAuthentication Loigout error

2021-08-26 Thread Juan Manuel Díaz Nevado
Hi, in my test i realize that there is some interaction with mongo registry tickets. When I set default tickets registry or now redis ticket registry there is no problem in logout, but mongo log is set in debug and no messages are displayed. Maybe i need to put on debug some other module than m