File(s): conf/relying-party.xml
Format: Native Spring
Overview
The Shibboleth.SSO profile configuration bean enables support for the SAML 1.1 Browser Single Sign-On profile initiated via the legacy Shibboleth request protocol, which is documented in the UnsolicitedSSOConfiguration page.
...
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.
The examples shown are not specific to any particular profile configuration.
| Localtabgroup |
|---|
| Include Page |
|---|
| ProfileConfiguration-Common |
|---|
| ProfileConfiguration-Common |
|---|
|
| Include Page |
|---|
| ProfileConfiguration-Authentication |
|---|
| ProfileConfiguration-Authentication |
|---|
|
| Include Page |
|---|
| ProfileConfiguration-SAML |
|---|
| ProfileConfiguration-SAML |
|---|
|
| Include Page |
|---|
| ProfileConfiguration-Artifact |
|---|
| ProfileConfiguration-Artifact |
|---|
|
| Include Page |
|---|
| ProfileConfiguration-ShibbolethSSO |
|---|
| ProfileConfiguration-ShibbolethSSO |
|---|
|
|
Notes
The default value of signResponses for this profile is "true", and it is unsafe to change this value. If you encounter a relying party that accepts an unsigned response that is transmitted via POST (and not artifact), you have identified an insecure implementation and should report the issue immediately while following your local security incident response process.