Hi!
I upgraded from CAS 6.1.x to 6.5.9 and got that to run with little
trouble (apart from per-Service-CORS).
Now I am getting reports that people cannot log in to a SAML-service and
looking in the log, I see
java.lang.IllegalArgumentException: SAML request or context could not be
Hello CAS Community,
I am currently upgrading from CAS server version 6.5.9 to version 6.6.1.
The CAS is deployed in production in a DOCKER container with the following
dependencies :
- org.apereo.cas:cas-server-support-ldap
- org.apereo.cas:cas-server-support-memcached-ticket-registry
-
On Tue, Oct 18, 2022 at 8:58 AM Michael Daley wrote:
> CAS: 6.1.7 Hazelcast ticket storage, ldap auth and attribute storage, duo
> MFA
>
> Recently experienced and issue where an attribute for Person A was
> released during Person B session.
>
You can put org.ldaptive in DEBUG to confirm the
CAS: 6.1.7 Hazelcast ticket storage, ldap auth and attribute storage, duo
MFA
Recently experienced and issue where an attribute for Person A was released
during Person B session. This caused Person B to have access to Person A's
mailbox (Office365).
Trying to track down if this is due to a
Hi Krishna,
finally we found problem, it was regarding tls protocol to use. Forcing use
of 1.2 works.
Thanks
Bye
Il giorno lunedì 17 ottobre 2022 alle 05:19:45 UTC+2 Krishna Prasad ha
scritto:
> Hi Andera,
>
> Please try to reproduce with simple jdbc program if possible. This mostly
>