ST-2026-117 · Authentication & identity
Atlassian CLI v1.3.15 requires OAuth re-authorisation for connected sites
Atlassian CLI v1.3.15 added OAuth scopes for upcoming features and security improvements, requiring a site administrator to re-authorise ACLI for every connected site.
Previous state
Existing connected sites operated under the prior ACLI OAuth permission set.
Current state
Until a site administrator upgrades ACLI and repeats the web OAuth consent flow, users can receive an authorisation error and cannot use ACLI normally with that site.
Affected users
Who needs to care
Atlassian CLI installations connected to Jira sites through the web OAuth flow.
Required response
What to do
Upgrade the site-admin installation, run acli jira auth login with the Web option and re-approve every affected site.
Evidence boundary
What the source does not prove
Atlassian states that no other behavioural changes are expected in v1.3.15. This is a connected-site OAuth consent change rather than a general Jira authentication migration.
Lifecycle history
Dated event sequence
- v1.3.15 permission change released
Additional OAuth scopes triggered site-admin re-authorisation for connected sites.
Evidence ledger
First-party sources
- 01Atlassian Developer — Atlassian CLI changelog
Official CLI changelog · 2026-03-25
Open official source ↗