OAuth tokens - IronBee

OAuth tokens are personal: each one belongs to you, in one account, and you can revoke it on its own. The IronBee CLI uses one to send data on your behalf. ironbee login creates one for you. Open Settings, then Personal > OAuth Tokens. For CI and deployment tooling, where no one signs in, use the shared account API key instead.

The tokens list

OAuth Tokens page with the Create token button and a list of tokens that are Active, Expiring soon or Never expires

OAuth Tokens page with the Create token button and a list of tokens that are Active, Expiring soon or Never expires

Column	What it shows
Token	The token’s name and the first characters of the token
Status	Active, Expiring soon (within 7 days), Expired or Never expires
Created	When the token was created
Expires	When the token expires, and how many days are left. A token that never expires shows `-`
Actions	Revoke the token

Create a token

Click Create token. The Create access token dialog opens.
Enter a Name, such as laptop or ci.
Choose an Expiration: 30 days, 60 days, 90 days (the default), 180 days, 1 year or No expiration.
Click Create token.

Create access token dialog with the Name field set to laptop and Expiration set to 90 days

Create access token dialog with the Name field set to laptop and Expiration set to 90 days

Copy your new access token shows the token once. Copy it, confirm you stored it, and click Done. It can’t be shown again. Tokens that ironbee login creates expire after 90 days. They’re named after your machine’s hostname, or the label you pass with ironbee login --name.

Revoke a token

Open the token’s ⋯ menu in the Actions column, choose Revoke, and click Revoke in Revoke this token?. The token stops sending data within a few minutes. This can’t be undone.

CLI authentication

How the CLI signs in and which credential it uses.

Account

The shared account API key for CI.