Repository navigation
fix(jira): say how to fix a scoped token sent to the site URL - #383
Open
21tmccauley wants to merge 2 commits into
Open
21tmccauley wants to merge 2 commits into
21tmccauley wants to merge 2 commits into
Conversation
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>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
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.