...
| Expand |
|---|
|
| Include Page |
|---|
| ProfileConfiguration-SAML |
|---|
| ProfileConfiguration-SAML |
|---|
|
|
| Expand |
|---|
|
Name | Type | Default | Desription |
|---|
signAssertions | Boolean | false | Whether to sign assertions |
|
Notes
The default value of signResponses for this profile 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.
Since SAML 1.1 does not support XML Encryption, all data is in plaintext, and therefore use of message-based security is not advisable.
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.