<Policy> element contains a couple of general settings and a configurable set of "rules" that implement particular protections and peer authentication mechanisms. You don't have to worry too much in general about unsafe behavior because if something disables all of the rules for authenticating a message, the system simply rejects it.
Uniquely names this policy within the configuration
Enables or disables schema validation of XML when parsing messages at runtime. Includes all SAML and SOAP messages.
|1 or more|
Security policy rules to apply
The default policy for dealing with SAML messages, in English, is:
- Don't schema validate.
- Check for replay, and reject messages older than 60 seconds in the past.
- Honor any SAML
<Condition>elements, including timestamps, and make sure the SP sees itself as an audience for any assertions. Reject any other conditions as unrecognized.
- Allow a message to be authenticated by checking for a TLS client certificate, an XML signature, and a "blob"-type signature, in that order. Anything present that can't be validated is fatal. Validation is based on the configured