...
| Expand |
|---|
|
| Include Page |
|---|
| ProfileConfiguration-SAML |
|---|
| ProfileConfiguration-SAML |
|---|
|
|
| Expand |
|---|
|
| Include Page |
|---|
| ProfileConfiguration-SAMLAssertion |
|---|
| ProfileConfiguration-SAMLAssertion |
|---|
|
|
| Expand |
|---|
|
| Include Page |
|---|
| ProfileConfiguration-SAML2 |
|---|
| ProfileConfiguration-SAML2 |
|---|
|
|
| Expand |
|---|
|
Name | Type | Default | Description |
|---|
encryptAssertions | Boolean | See Notes | Whether to encrypt assertions | encryptAttributes | Boolean | false | Whether to encrypt attributes |
|
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.
The default value of encryptAssertions is also conditional on the same basis.
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.