Understand the signed portal-to-authority contract used to issue and manage customer licenses.

Architecture

The billing portal signs server-to-server management requests with a portal client ID and a 32-byte HMAC secret. The authority validates timestamp, nonce, signature, source IP and idempotency key before operating on a license owned by that portal customer reference.

Lifecycle actions

ActionUsepingVerify credentials and connectivity.issueCreate the paid customer license and return its public record.statusSynchronize license and installation telemetry.renewAdvance the paid license term.suspend / reactivate / terminateMirror service lifecycle state.reissueDeactivate former installation bindings for a controlled move.downloadIssue a short-lived, single-use stable-package token.

Security properties

• TLS peer and hostname verification stay enabled.
• Nonces and timestamps prevent replay.
• Idempotency prevents duplicate lifecycle mutations.
• Activation keys are encrypted in the billing portal and hashed by the authority.
• Download tokens are short-lived, one-use and bound to the requesting portal server.