...
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.
Expand |
---|
|
Include Page |
---|
| ProfileConfiguration-Common |
---|
| ProfileConfiguration-Common |
---|
|
|
Expand |
---|
|
Include Page |
---|
| ProfileConfiguration-SAML |
---|
| ProfileConfiguration-SAML |
---|
|
|
Expand |
---|
|
Include Page |
---|
| IDP30:ProfileConfiguration-SAML2 |
---|
| IDP30:ProfileConfiguration-SAML2 |
---|
|
|
...
|
Include Page |
---|
| ProfileConfiguration-SAML2SSO |
---|
| ProfileConfiguration-SAML2SSO |
---|
|
|
Expand |
---|
|
ECP-specific settings: Name | Type | Description |
---|
localEvents | Collection<String> | Identifies webflow events that should be handled without use of a SOAP fault |
|
Notes
The default value of signResponses
for this profile is "true", in keeping with modern best practice. As long as one of the response or assertion are signed, use of the profile is "safe" in terms of authentication integrity, but there are vulnerabilities in XML Encryption that make signing responses advisable when the most common encryption algorithms are used. Some of the backstory around the signing defaults is discussed in this thread.
...
If you encounter a relying party that accepts an unsigned response and assertion that is transmitted via POST (and not artifact)the ECP profile, you have identified an insecure implementation and should report the issue immediately while following your local security incident response process.
...