Skip to content

Select and authorize signing certificates by request context #9446

Open

Description

@vitormattos

Goal

Automatically suggest and securely authorize the appropriate personal signing certificate for each signature request, considering its organizational context and the signer's eligible certificates.

Confirmed requirements

  • Associate signing requests with a backend-validated organizational context when applicable.
  • Preserve the relevant context and resolved policy across the signing lifecycle.
  • When a request belongs to organization A, prefer an eligible certificate associated with A.
  • When a request belongs to organization B, prefer an eligible certificate associated with B.
  • Support users belonging to multiple groups and owning multiple certificates.
  • Allow manual selection among certificates permitted by the request policy.
  • Allow certificates from another organization or external issuer only when explicitly permitted.
  • Support one optional global default certificate per user without overriding context-specific eligibility.
  • Prompt for selection when multiple eligible certificates remain and no unambiguous default exists.
  • Handle missing, expired, revoked, disabled and inaccessible certificates.
  • Prevent unauthorized cross-context use through backend checks, including immediately before signing.
  • Preserve the distinction between persistent certificates and temporary Click to Sign certificates.
  • Record the effective certificate and issuer used for signing without exposing private keys or passwords.
  • Preserve validation and auditability of previously signed documents.

Questions to resolve

  • Which event establishes the organizational context of a signing request.
  • Whether the context may differ for individual signers in the same request.
  • Handling an external signer who is not a member of the requesting organization.
  • The precise eligibility rules for imported certificates.
  • The treatment of group membership changes after a request is created.
  • Recovery and UX when no eligible certificate exists.

Planning gate

Implementation depends on the certificate inventory and issuer/context contracts. UX prototypes and simulated contract tests may proceed before those integrations are available.

Done when

  • Certificate selection is predictable for multi-group users.
  • Request policy determines eligibility; frontend choices cannot bypass it.
  • Temporary, imported and persistent certificate flows remain functional.
  • Automated integration and browser tests cover eligible, ambiguous and prohibited selections.
  • Existing signed PDFs remain valid and signing documentation is updated.

Metadata

Metadata

Assignees

No one assigned

    Labels

    Type

    Fields

    Priority

    None yet

    Projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions