Cryptographic Exchanges
What this screen is for
A cryptographic exchange is a governed binding between two endpoints — one of your applications and another, or an external counterparty — inside one exchange context, with the grants that say which identities may do what, with which keys. It is managed as a single lifecycle. This screen lists every exchange in your tenant in every state, opens one to work on it, and starts a new one.
The composing happens in the editor, which is where an exchange gets its endpoints, context and grants, and is validated, activated, suspended and revoked:
What must exist first
This screen is for tenants that compose authorization by hand. It is not offered to SIMPLE tenants: a SIMPLE tenant uses Internal Use Cases.
Before you work here:
- The permission to read cryptographic exchanges. Without it the screen opens and reports the refusal where the list would be.
- The permission to create cryptographic exchanges, for New exchange. Without it the control is shown disabled and says which permission to ask for.
Decisions you make here
Reading the list
Each row shows the exchange's name, its status, Origin → destination with the relationship beneath it, its Exchange Context, its Live grants, its Validity window and when it was Last modified. The relationship is derived from the endpoints: Same application (A → A), Internal (A → B), Outbound (A → external) or Inbound (external → A).
The status is the exchange's own lifecycle: DRAFT while it is being composed, READY once validated, ACTIVE while its grants authorize, SUSPENDED while that is paused, and EXPIRED, CONSUMED or REVOKED once it has ended for good. An ended exchange shows why: Expired, Consumed — grant used up, Revoked by an operator, Revoked — key destroyed, Revoked — tenant closed, Revoked — application deleted or Revoked — context closed.
Several things end an exchange without anyone acting on it. It stops working at its effective until instant, and the expiry job then shows it as EXPIRED. It becomes CONSUMED when its last live grant is used up. It is revoked when an application at one of its ends is deleted, when the key its last live grant names is destroyed, and when its exchange context is closed.
The status does not show a suspended exchange context. Suspending a context stops every grant in it, but its exchanges keep saying ACTIVE here. Read the context's status before concluding that a relationship is live.
Filtering and sorting
All statuses narrows the list to one status. Counterparty matches part of an external endpoint's name, ignoring case. Search by name matches part of the exchange's name. The filters combine.
The list is sorted by last modified, newest first; you can sort by name, status, effective until or creation date instead. When a filter leaves nothing, the screen says which filters are applied and offers to clear them.
Opening and creating an exchange
Clicking a row opens that exchange in the editor, whatever its status. New exchange opens the editor on a new draft, which appears in this list once saved. A draft authorizes nothing until it is activated.
How it relates to other screens
Every exchange belongs to one exchange context, whose status is managed on its own screen. Closing a context revokes its exchanges:
An exchange's grants are listed with the others on Capability Grants:
The topology draws your exchanges as directed lines between their endpoints:
Deleting an application revokes the exchanges it is an endpoint of, and destroying a key retires the grants that name it: