Revoke a trust relationship

A cooperation is ending, or a partner must stop opening connections right now, and you don't want to wait for the partner to agree.

You revoke your direction of the relationship in your own ledger. From then on, your TLS adapter accepts no new connections for this relationship, your key agent agrees on no new secrets, and the existing secrets are deleted. The other side doesn't need to agree.

1. Revoke your direction of the relationship with the partner management role. The revocation is recorded in the ledger together with the approving person.
2. The CA worker produces a new trust bundle without the relationship, and the TLS adapters load it.
3. If management is unavailable, revoke at the console of the worker host. The new bundle reaches the adapters over the second path.
4. Let the other side know while it's still reachable through the relationship. The revocation takes effect even without notice.

Result. New connections are refused immediately. Existing connections end no later than the period set in the relationship policy, by default 15 minutes. The revocation, the approving person, and the time are recorded in your organization's ledger.

• Revoking a relationship isn't revoking a certificate. The other side's certificates remain valid, and its connections to other organizations are unaffected.
• When you revoke at the console, the lifetime of the old bundle bounds the effect until the adapters have the new one; by default that's 24 hours at most.
• The “relationship revocation” emergency test checks under live traffic that new connections are refused at once and existing ones end within the period.

• Federation and bilateral trust – what revocation and termination do
• Operations and emergencies – revocation without management
• Revoke a certificate