Hey
Thanks for those suggestions - finally got to the bottom of it - and Ray,
you were on the right lines...
The IDP metadata we had got from the client was 'prettily' formatted, which
included helpfully adding carriage returns and spaces after the
X509Certificate start tag and before the end
For JWT as a service, what is the appropriate CAS Validation Filter to use
on the client side? Or does this have to be custom Filter where I need to
verify the signature, decode, and create the Assertion with principle?
On Thursday, March 30, 2023 at 11:05:28 AM UTC-5 Pablo Vidaurri wrote:
> I'
Hi All
Does anyone have an example of what should be in the cas.properties file?
I'm installing a new server with this version of CAS and I've never used it
before. My last install was cas5.x
Anyway, I'd love to see an example
thank you
Jen
--
- Website: https://apereo.github.io/cas
- Gitt
Chris,
It could be that the vendor is using an encryption certificate different from
the one you are expecting.
Ray
On Thu, 2023-03-30 at 19:58 -0700, 'Chris Durham' via CAS Community wrote:
Notice: This message was sent from outside the University of Victoria email
system. Please be cautious
PUBLIC / CYHOEDDUS
Thanks for the heads up Ray,
We will now remove the expiring Azure certificate shortly after successfully
testing the rollover, and use the /cas/sp/idp/metadata?force=true endpoint on
our CAS server whenever our Azure service’s metadata changes.
Kevin
From: cas-user@apereo.or
Check the system times (ntp) between the two hosts.
-Jeff
On Fri, Mar 31, 2023 at 1:11 AM 'Chris Durham' via CAS Community <
cas-user@apereo.org> wrote:
> 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
