Repository navigation
Description
Enhancement Description
Make SAML identity-provider signature settings express independently whether response signatures and assertion signatures are required. Introduce a Want Responses Signed setting alongside Want Assertions Signed, and deprecate or replace Validate Signature.
Currently, Validate Signature does not consistently mean that the response itself must be signed: for POST binding, a signed assertion can satisfy validation without a response signature. Administrators should be able to explicitly require signed responses, signed assertions, or both, with cryptographic verification of every required signature.
This follows the secure-default work in #54749, which explicitly leaves settings redesign out of scope.
Value Proposition
Provide clear, predictable signature requirements and encourage configurations that protect both the response and its assertions. Avoid requiring administrators to understand implicit interactions between signature presence, signature verification, and binding-specific behavior.
Goals
- Provide independent settings for requiring response and assertion signatures.
- Default both requirements to enabled for newly created SAML identity providers.
- Reject missing or invalid signatures whenever the corresponding requirement is enabled.
- Define consistent semantics across POST, Redirect, and Artifact bindings, including encrypted assertions.
- Define migration from existing
validateSignatureandwantAssertionsSignedcombinations, documenting any intentional compatibility changes. - Align the Admin Console, Admin REST API, imports, and metadata handling with the new settings.
- Cover supported combinations and migration behavior with regression tests.
Non-Goals
- Change OIDC identity-provider settings or SAML client settings.
- Redesign SAML signing algorithms or key management.
- Repeat the omitted-setting default changes covered by SAML Default signature validation securely when settings are omitted #54749.
Discussion
Notes
The following decisions should be resolved as part of the design:
- Should disabling both signature requirements be prohibited, or remain an explicit compatibility opt-out?
- Should Validate Signature be deprecated with a transition period or replaced directly?
- How should existing configurations retain their intended behavior without silently weakening validation?
- What constitutes a response signature for each binding, particularly the ArtifactResponse wrapper versus its embedded response?
- How should signature requirements for logout requests and responses be represented, given that Validate Signature currently also controls them?
Metadata
Metadata
Assignees
Labels
Type
Fields
Value
Effort
Votes
Projects
- StatusShow more project fieldsOpen
Activity