Skip to content

jira auth migrate

  • Usage: jira auth migrate [flags]

Move stored credentials between supported secret backends while keeping each profile's Jira metadata. Use it when switching from the OS keyring to 1Password, or when moving a profile back to the keyring.

--dry-run previews the migration plan without reading or writing secrets. Real migrations stage destination writes before saving config, then clean up old storage where jira-cli owns it.

Safety

--dry-run

Preview credential migration

1Password

--item <NAME>

1Password item name

--onepassword-account <ACCOUNT>

1Password desktop app account name

--vault <VAULT>

1Password vault name

Options

--backend <BACKEND>

Target secret backend for the credential

Allowed values:

  • keyring — OS keychain (default)
  • 1password — 1Password CLI

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
cleanup_failures[] string
cleanup_notes[] string
dry_run boolean
profiles[] object
target_backend string

Examples

jira auth migrate --backend 1password --vault Private --dry-run # (1)!
jira auth migrate --profile work --backend 1password --vault Private --item jira-work # (2)!
jira auth migrate --profile work --backend keyring # (3)!
  1. Preview migrating every profile's credential to 1Password
  2. Migrate one profile's credential into a 1Password vault item
  3. Move a profile's credential back to the OS keyring