Jorge,
The idea is that a web application should authenticate a user against CAS, and then it should establish its own *application session*.
The CAS service ticket is no longer useful at this point (it is expired).
The CAS TGC stays active so if you want to authenticate to an entirely different web application that also uses CAS, you will be issued a new ST for that service, and once validated, that web application would establish its own application session.
The idea is not that a web application should authenticate ever HTTP request against CAS.
Thanks,
Carl Waldbieser
ITS Identity Management
Lafayette College
--
----
Si usted no es destinatario y recibió este correo por error, agradeceremos
que proceda a borrarlo. Por favor no copie, use ni divulge su contenido.
If you are not the intended recipient and receive this e-mail in error,
please delete it. Please do not copy, use and not disclose its contents.
Antes de imprimir... Piense en su compromiso con el medio ambiente.
--
- CAS gitter chatroom:
https://gitter.im/apereo/cas
- CAS mailing list guidelines:
https://apereo.github.io/cas/Mailing-Lists.html
- CAS documentation website:
https://apereo.github.io/cas
- CAS project website:
https://github.com/apereo/cas
---
You received this message because you are subscribed to the Google Groups "CAS Community" group.
To unsubscribe from this group and stop receiving emails from it, send an email to
cas-user+u...@apereo.org.
To view this discussion on the web visit
https://groups.google.com/a/apereo.org/d/msgid/cas-user/3e3723ea-468f-4166-8547-e2d4fb242048%40apereo.org.