SAML1ArtifactResolutionConfiguration

File(s): conf/relying-party.xml

Format: Native Spring

Overview

The SAML1.ArtifactResolution profile configuration bean enables support for the SAML 1.1 Artifact Resolution profile over SOAP. It is required when supporting the use of the Artifact profile with Browser SSO in order to deliver the full assertion. It should be disabled if not in use.

Configuration

The most typical options used are described in more detail below, but not every obscure option is discussed. See the javadoc for all of the possible configuration options for this profile (note that many of them are inherited from parent classes).

Virtually all the configuration options below can be set via two different properties: a static property that explicitly sets the value to use and a lookup strategy or predicate property that takes a Function or Predicate and returns the value to use. The dynamic property is generally named "propertyNamePredicate" or "propertyNameLookupStrategy" for Boolean- and non-Boolean-valued properties respectively.

Name

Type

Default

Desription

Name

Type

Default

Desription

signAssertions

Boolean

false

Whether to sign assertions

Notes

The default value of signResponses for this profile signs only if TLS isn't used (very unusual) or if the receiving port is 443. It assumes that traffic over 443 will be relying on message-based security measures, whereas traffic to an alternative TLS port like 8443 will be relying on mutual authentication and thus provide a secure channel.

Since SAML 1.1 does not support XML Encryption, all data is in plaintext, and therefore use of message-based security is not advisable.

If you need to enable the signAssertions option, and you control the SP's metadata, you should generally add the WantAssertionsSigned flag to it in place of using this option. Related, the idp.saml.honorWantAssertionsSigned property can be turned off to globally ignore that flag in metadata should you wish to do so.

Â