We have a SAML SP (3rd Party system) that has multiple signing keys in 
their metadata. They rotate keys, yearly, from a Public Certificate 
Authority. CAS picks either the first key or the one with the furthest 
expiration date, I don't know which, but I do know it's picking the wrong 
certificate. Is there a way to influence this behavior, so I can use their 
hosted, on the internet, metadata, rather than having to copy and update 
locally?

Thank you in advance!

Thank you,
Matt

-- 
- Website: https://apereo.github.io/cas
- Gitter Chatroom: https://gitter.im/apereo/cas
- List Guidelines: https://goo.gl/1VRrw7
- Contributions: https://goo.gl/mh7qDG
--- 
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+unsubscr...@apereo.org.
To view this discussion on the web visit 
https://groups.google.com/a/apereo.org/d/msgid/cas-user/8057dbe4-13a1-4284-b5f3-68a0f90e2dffn%40apereo.org.

Reply via email to