-
Notifications
You must be signed in to change notification settings - Fork 3
Open
Description
Summary
The current CLI authentication options are confusing for Jira Cloud users. The --jira.password option is used with API tokens, but the naming suggests a password.
Current State
For Jira Cloud API token authentication, users must use:
--jira.username your-email@example.com \
--jira.password YOUR_API_TOKENThis is counterintuitive since the "password" is actually an API token.
Proposed Change
Add a --jira.apiToken alias (or alternative option) that makes Jira Cloud authentication clearer:
--jira.username your-email@example.com \
--jira.apiToken YOUR_API_TOKENImplementation Notes
- Could be a simple alias to
--jira.passwordin the yargs configuration - Or a new dedicated auth method
jiraClientWithApiToken(email, apiToken)for clarity - Should update help text to explain the difference between Server PAT and Cloud API tokens
Auth Methods Reference
| Jira Type | Current Option | Auth Style |
|---|---|---|
| Server/DC PAT | --jira.personalAccessToken |
Bearer token |
| Cloud API Token | --jira.username + --jira.password |
Basic auth |
| OAuth | Consumer key/secret + access tokens | OAuth 1.0a |
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
No labels