Skip to content

fix(jira): say how to fix a scoped token sent to the site URL - #383

Open
21tmccauley wants to merge 2 commits into
mainfrom
fix/jira-scoped-token-hint
Open

21tmccauley wants to merge 2 commits into
mainfrom
fix/jira-scoped-token-hint

Conversation

@21tmccauley

Copy link
Copy Markdown
Collaborator

Jira answers "401 Unauthorized; scope does not match" on every call when a scoped API token is used with JIRA_BASE_URL set to the site URL, since scoped tokens only work through the API gateway. Before, the run failed with a generic auth_failed. Now it stops at the first call with bad_config and names the gateway URL and the site's _edge/tenant_info link for the cloudId. Through the gateway the same answer means a missing scope and is reported as not_authorized.

The README now lists all four Jira fetchers that need no admin permission, and adds sections on running without Jira admin access and on reading the "scope does not match" error.

21tmccauley and others added 2 commits November 17, 2026 13:08
Jira answers "401 Unauthorized; scope does not match" on every call when
a scoped API token is used with JIRA_BASE_URL set to the site URL, since
scoped tokens only work through the API gateway. Before, the run failed
with a generic auth_failed. Now it stops at the first call with
bad_config and names the gateway URL and the site's _edge/tenant_info
link for the cloudId. Through the gateway the same answer means a
missing scope and is reported as not_authorized.

The README now lists all four Jira fetchers that need no admin
permission, and adds sections on running without Jira admin access and
on reading the "scope does not match" error.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
…f scopes

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant