File(s): conf/relying-party.xml
Format: Native Spring
Overview
The SAML2.AttributeQuery profile configuration bean enables support for the SAML 2.0 Attribute Query profile over SOAP. It was implemented mostly for completeness and has seen some use by virtual organizations and research communities but is rarely used in enterprise scenarios.
...
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.
| Localtabgroup |
|---|
| Include Page |
|---|
| ProfileConfiguration-Common |
|---|
| ProfileConfiguration-Common |
|---|
|
| Include Page |
|---|
| ProfileConfiguration-SAML |
|---|
| ProfileConfiguration-SAML |
|---|
|
| Include Page |
|---|
| ProfileConfiguration-SAML2 |
|---|
| ProfileConfiguration-SAML2 |
|---|
|
|
Notes
The default value of signResponses for this profile is an extended form of the behavior that was referred to in V2 as "conditional". It 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 (but see below), whereas traffic to an alternative TLS port like 8443 will be relying on mutual authentication and thus provide a secure channel.
...