Approval policies

Choose how an io.sign Virtual Signer decides whether to participate

Before participating in key generation, resharing, or signing, a Virtual Signer evaluates an approval policy. The policy returns approve, reject, or abstain; only approve makes the signer available to the operation. With manual approval, an approver system makes the decision instead, through a signed API call: for every request, or for the requests your policy answers with defer.

Supported modes

ModeUse
Custom policy serverApply policy in an HTTPS service operated by your organisation.
Open Policy Agent (OPA)Evaluate Rego policies through OPA's Data API and a TLS path adapter.
Manual approvalHold requests until an approver system approves or rejects them, on its own or for requests your policy defers.
Always approveSmoke-test a development deployment only. Never assign production signing power to this mode.

OPA and custom servers use the same Broker mode and wire contract. Set IOSIGN_SIGNER_BROKER_APPROVAL_MODE=api-approval; the configured HTTPS service determines whether the target is OPA or your application.

Fail-closed behaviour

The Virtual Signer rejects the request when the policy service can't provide a valid decision. The Broker retries network failures and HTTP 5xx responses, and rejects invalid responses and HTTP 4xx responses without retrying. See Custom policy server for the exact behaviour.

Choose a policy engine

  • Choose OPA when your team wants version-controlled, testable Rego policy and can operate OPA behind a TLS adapter.
  • Choose a custom policy server when decisions require an existing risk service, database, workflow, or implementation language.
  • Add manual approval when some or all decisions need a person or a workflow that takes longer than a policy call.
  • Use Always approve only long enough to verify non-production connectivity.

Did this page help you?