tigby key
Create and revoke API keys
Admin Keys act for the whole Org; Identity Keys are minted with an Identity and act for that one Identity. Both are listed here, and both are revoked here.
tigby key create
Mint an Admin Key.
The key is in the answer exactly once. It is not stored in the profile; use tigby login for that.
tigby key create <name> [options]| Argument | What it is |
|---|---|
<name> | A label, such as the agent or host that will hold the key. |
tigby key create ci-runnertigby key list
List the Org's live keys.
tigby key list [options]tigby key rotate
Replace this profile's key with a fresh one.
Mints a new Admin Key under the same name, writes it to the profile, and revokes the old one. Anything else still using the old key stops working at that moment.
tigby key rotate [options]This command cannot be undone, so it asks before it acts. --yes answers in advance; --json implies it.
tigby key revoke
Revoke a key by id.
The key is refused from the next request on. Revoking an Identity Key also severs that Identity's live Tunnel – the traffic it is carrying ends mid-request – because a connection is authorized once, when the agent connects, and would otherwise keep serving under the revoked key. A tunnel server that cannot be reached is owed the sever and retried until it confirms. Revoking a key that is already revoked changes nothing about the row and severs again.
tigby key revoke <id> [options]| Argument | What it is |
|---|---|
<id> | The key's id, as tigby key list shows it. |
This command cannot be undone, so it asks before it acts. --yes answers in advance; --json implies it.