Bear all,
I implemented two approaches:
1. Passing the SAML artifacts in the URL
2. Creating a new TST for each SAML request and passing it as parameter
(do not store artifacts in the session).
Although both of them work in our setup, I do not like them completely.
Misagh commented
Good morning!
I'd like to gather some opinions on the following implementation idea. I'm
planning to create a facade for the SessionStore called
StackableSessionStore. The purpose of this facade is to handle the storage
of the TST (Ticket Storage Token) in a new session object that won't be
Dear Ray, Jerôme,
I have asked colleagues in other universities and they reproduce the same
problem. We are interested in collaborate and propose an improvement to the
web flow. I have checked the code and as I see it I will need to change a
few core classes. At a minimum, I think that the
Thank you, Ray. Best regards
El viernes, 9 de junio de 2023 a las 18:39:53 UTC+2, Ray Bon escribió:
> Miguel,
>
> This sounds like what Jérôme talked about in this thread
> https://groups.google.com/a/apereo.org/g/cas-user/c/fNZ82V32sio/m/RKhi5VQCAQAJ?utm_medium=email_source=footer
>
> Ray
>
>
Miguel,
This sounds like what Jérôme talked about in this thread
https://groups.google.com/a/apereo.org/g/cas-user/c/fNZ82V32sio/m/RKhi5VQCAQAJ?utm_medium=email_source=footer
Ray
On Fri, 2023-06-09 at 05:03 -0700, Miguel Martínez De Espronceda Cámara wrote:
Notice: This message was sent from
Dear all,
I am reaching out regarding the use of CAS 6.6.8 for serving SAML2
requests. Currently, we are in the process of migrating our Google
integration from the deprecated Google-native integration to standard SAML2
endpoints. To provide some context, the deprecated module was designed to
