...
| Expand |
|---|
|
| Include Page |
|---|
| ProfileConfiguration-Common |
|---|
| ProfileConfiguration-Common |
|---|
|
|
| Expand |
|---|
|
| Include Page |
|---|
| ProfileConfiguration-Authentication |
|---|
| ProfileConfiguration-Authentication |
|---|
|
|
| Expand |
|---|
|
| Include Page |
|---|
| ProfileConfiguration-SAML |
|---|
| ProfileConfiguration-SAML |
|---|
|
|
| Expand |
|---|
|
| Include Page |
|---|
| ProfileConfiguration-SAML2 |
|---|
| ProfileConfiguration-SAML2 |
|---|
|
|
| Expand |
|---|
|
| Include Page |
|---|
| ProfileConfiguration-Artifact |
|---|
| ProfileConfiguration-Artifact |
|---|
|
|
| Expand |
|---|
|
| Include Page |
|---|
| ProfileConfiguration-SAML2SSO |
|---|
| ProfileConfiguration-SAML2SSO |
|---|
|
|
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.
...