Skip to content

Introduce independent response and assertion signature requirements for SAML identity providers #55249

Description

@pedroigor

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 validateSignature and wantAssertionsSigned combinations, 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

Discussion

#53868 (comment)

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

No one assigned

    Labels

    Fields

    Value

    None yet

    Effort

    None yet

    Votes

    None yet

    Projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions