On a CAS 6.5 system, we're trying to troubleshoot a problem with one of our CAS clients applications. One experiment we'd like to try is to increase cas.saml-core.skew-allowance from its default 30s to perhaps 40s.
Ideally we'd like to try this on a per-service basis to limit the scope of the change, but I don't see an example of this in the documentation at < https://apereo.github.io/cas/6.5.x/protocol/SAML-Protocol.html#configuration > Perhaps something like: { "@class" : "org.apereo.cas.services.RegexRegisteredService", "serviceId" : "^https://.*";, "name" : "Sample", "id" : 10, "notSureWhatIdentifierToUseHere": { "@class": " org.apereo.cas.configuration.model.support.saml.SamlCoreProperties", "skew-allowance": PT40S } } This was modeled from the example for cas.ticket.st.time-to-kill-in-seconds at < https://apereo.github.io/cas/6.5.x/ticketing/Configuring-Ticket-Expiration-Policy.html#per-service>. However, assuming this is possible, I don't know what would be appropriate where I have the placeholder "notSureWhatIdentifierToUseHere". -- Baron Fujimoto <[email protected]> ::: UH Information Technology Services minutas cantorum, minutas balorum, minutas carboratum descendus pantorum -- - 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 [email protected]. To view this discussion on the web visit https://groups.google.com/a/apereo.org/d/msgid/cas-user/CAAjLUL2JpgGuX9dY8Jm_JowzOUr4jK28V7TyJ5pkQpsE1fz1gA%40mail.gmail.com.
