I'm following this to setup JWT as a service ticket:
https://apereo.github.io/cas/6.5.x/installation/Configure-ServiceTicket-JWT.html
I am using global keys and not defining them in service json file.
I am able to login but get a failure when validating the ST. Looks like the
ST being check is
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
PUBLIC / CYHOEDDUS
Hi,
We are delegating our CAS authentication to Azure via SAML using
cas.authn.pac4j.saml. We've been doing that for 3 years, without any issues.
Our Azure CAS app's SAML certificate is due to expire shortly.
We are planning to renew the certificate, make it active, and delete
Kevin,
Here is an example of cert rollover,
https://www.switch.ch/aai/guides/idp/certificate-rollover/
The expired certs will prevent log in if the applications are not broken.
Ray
On Thu, 2023-03-30 at 15:54 +, 'Kevin Sewell' via CAS Community wrote:
Notice: This message was sent from out
Hi,
We've got CAS 6.6.x running beautifully with delegated IDP logins to
multiple SAML providers, but the most recent one we've had to integrate
with is causing me some headaches.
The initial redirect works fine, but when it comes back CAS displays the
SAML message but then fails to decrypt th
