jira auth logout¶
- Usage:
jira auth logout PROFILE [flags]
Remove the stored credential for one profile from its configured secret backend. Use it when a token is no longer valid or a machine should stop using that Jira account.
The profile entry remains in config, so site metadata and defaults are kept. If no credential exists, the command succeeds and reports removed: false.
Removing a credential is destructive — getting it back means re-entering the token. --dry-run reports the credential a live logout would remove without touching the backend. A live logout requires --force in headless, agent, or --no-input mode; an interactive terminal proceeds without a prompt — naming the profile is the intent.
A credential can outlive its profile: deleting the profile from config does not remove the stored secret. The keychain entry is keyed by site host and profile name, so passing --base-url supplies the missing half of that identity and lets logout purge the orphaned credential.
Safety¶
--dry-run¶
Report the credential a live logout would remove without touching the backend
--force¶
Confirm the credential removal in headless / agent / --no-input mode
Configuration¶
--base-url <URL>¶
Jira site of the credential to remove; required to purge a credential whose profile was deleted from config
Output fields¶
With --output json, the response envelope's data object carries these fields. Run jira agent schema for the full machine-readable schema.
| Field | Type | Description |
|---|---|---|
backend |
string | |
dry_run |
boolean | |
profile |
string | |
removed |
boolean |
Examples¶
jira auth logout work
jira auth logout work --force --output=json # (1)!
jira auth logout work --dry-run --output=json # (2)!
jira auth logout old-work --base-url acme.atlassian.net # (3)!
- Report whether a credential was removed
- Report which credential would be removed, without removing it
- Purge the credential of a profile already deleted from config