Connections Created with metadataUrl Parameter Do Not Allow Updating Signed Requests Setting
Last Updated:
Overview
When using the method described in the article Creating SAML Enterprise Connection from Customer Provided Metadata Files to use the metadataUrl parameter to create a SAML connection, it is impossible to set "Signed Requests" = True. The toggle resets itself after pressing Save. This article provides a potential solution to this issue.
Applies To
- Connections
- Metadata URL
Solution
The signSamlRequest attribute will be set based on the "WantAuthnRequestsSigned" attribute in the Identity Providers (IdP) metadata.
When an update is made to a connection through the dashboard or Management API that was created using the IdPs "metadataUrl", it will pull the metadata again and the signSamlRequest option will be superseded by the metadata.
If the IdP is specifying the WantAuthnRequestsSigned as false, it could be expected they will reject signed requests, so this synchronisation is in place to better align the connection with the IdP's declarations for ease of use.
