docs(jira): document browser OAuth (PKCE) login#13
Open
mintlify[bot] wants to merge 1 commit into
Open
Conversation
Author
|
Preview deployment for your docs. Learn more about Mintlify Previews.
|
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.
Summary
Rewrite the Jira integration guide to lead with the new one-command browser OAuth flow, and surface the supporting CLI command and environment variable in the reference pages.
Changes
guides/jira.mdx: lead withmeridian oauth-login jira(Authorization Code + PKCE). Document the token store at~/.meridian/oauth/jira.json(mode 0600, auto-refresh with rotating refresh tokens), the requested scopes (read:jira-work,write:jira-work,read:jira-user,offline_access), the resolver order (OAuth wins when the token store exists, basic auth as fallback), and theJIRA_OAUTH_CLIENT_IDoverride for self-hosted Atlassian apps. Keep the API-token path as a documented fallback for org-blocked installs.reference/cli.mdx: add accordions formeridian oauth-login jiraandmeridian tasks-sync.reference/environment-variables.mdx: clarify that Jira is configured when either the OAuth token store or all three static creds are present; addJIRA_OAUTH_CLIENT_ID.Context
Source PRs: Meridiona/meridian#203 (OAuth implementation) and Meridiona/meridian#213 (installer integration + maintainer runbook). Linear OAuth is held for a follow-up.