Skip to main content

Documentation Index

Fetch the complete documentation index at: https://authsome.agentr.dev/docs/llms.txt

Use this file to discover all available pages before exploring further.

Atlassian is a bundled OAuth2 provider in authsome. Jira and Confluence Cloud APIs.

​
At a glance

Provider nameatlassian
Display nameAtlassian
Auth typeOAuth2
Default flowpkce, PKCE browser flow
PKCE supportedYes
Device code supportedNo
DCR supportedNo
Default scopesread:jira-work, write:jira-work, read:jira-user, manage:jira-project, manage:jira-configuration
Proxy hostapi.atlassian.com
Env var (access_token)ATLASSIAN_ACCESS_TOKEN
Env var (refresh_token)ATLASSIAN_REFRESH_TOKEN

​
Prerequisites

You need to register an OAuth app with Atlassian once. Atlassian’s OAuth model is per-app. Register an app at the developer console, set the callback URL, and copy the client ID and secret. The redirect URI must be: 
http://127.0.0.1:7998/auth/callback/oauth
This is the only callback URL authsome’s PKCE flow listens on. Dashboard: https://developer.atlassian.com/console/myapps/.

​
Log in

uvx authsome login atlassian
The first time, authsome opens a local form at http://127.0.0.1:7998 to collect your client_id and client_secret. They are encrypted under your profile and reused on every subsequent login. A second browser window then opens to https://auth.atlassian.com/authorize for the authorization step. Verify: 
uvx authsome get atlassian --field status
# → connected

​
Custom scopes

The bundled definition requests read:jira-work, write:jira-work, read:jira-user, manage:jira-project, manage:jira-configuration. Override at login time: 
uvx authsome login atlassian --scopes "<comma-separated>"
The granted scopes are stored on the connection and visible in uvx authsome get atlassian.

​
Multiple accounts

Pass --connection <name> on login and on every read command to keep two or more accounts on the same provider side by side. See Multiple connections per provider for the full pattern. 
uvx authsome login atlassian --connection personal
uvx authsome login atlassian --connection work

​
Use the token

Run the agent under the proxy. The library tab is for embedding authsome inside a larger Python orchestrator. 
uvx authsome run -- python my_agent.py
Under the proxy, authsome sets ATLASSIAN_ACCESS_TOKEN=authsome-proxy-managed in the child’s environment and injects the real token into outbound requests to api.atlassian.com. The child process never sees the actual value. Refresh tokens are never exported.

​
Override the bundled definition

uvx authsome inspect atlassian > ~/.authsome/providers/atlassian.json
# edit scopes, base_url, or anything else
uvx authsome list   # source now shows "custom" for atlassian
User-registered files always win over bundled definitions. See Provider schema.

​
What’s next

Run agents with the proxy

Inject the access token into outbound requests without exposing it.

Multiple connections per provider

Keep two or more accounts on the same provider side by side.

Provider schema

Every field in a provider definition.

OAuth providers

All bundled OAuth providers.