Feature: Add username/password Basic authentication for Jira Server/Data Center
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 35/100
- Issue type
- Feature
- Clarity
- Clearly specified
- Activity status
- Active
- Tech stack
- csharp
- Domain
- authentication, backend-api-design, security
Research direction
Start by reading the existing Jira Cloud authentication, host validation, credential storage, and REST client code, then inspect the tests for current Cloud connections. Confirm which Jira Server/Data Center API versions and endpoints the app supports. Done means adding the new authentication mode with host binding, HTTPS and secret handling, Cloud rejection, and automated regression coverage; this is a broad security-sensitive change.
Written by the indexing model from the issue text.
Description
Summary
Add an authentication option that uses HTTP Basic authentication with a Jira username and password.
This mode is intended for Jira Server/Data Center instances that still permit username/password REST authentication. Jira Cloud does not accept Atlassian account passwords for REST Basic authentication, so Cloud connections must continue to use email plus API token.
Motivation
Some Jira Server/Data Center environments use local Jira accounts and Basic authentication rather than Atlassian Cloud API tokens. JiraTaskBar currently models credentials as Jira Cloud email plus API token and restricts connections to Atlassian Cloud hosts.
Proposed behaviour
- Add an authentication-method selector in Settings:
- Jira Cloud API token (existing)
- Jira Server/Data Center username and password (new)
- Show context-appropriate field labels and guidance for each method.
- Send the Server/Data Center credential using
Authorization: Basic base64(username:password). - Require HTTPS and retain normal TLS certificate validation.
- Never log the username/password, encoded Authorization header, or credential contents.
- Store the username, password, and target site as one protected credential so a saved credential cannot be redirected to a different host.
- Provide a clear action to forget/delete the saved credential.
- Reject or clearly explain username/password mode when the target is an
atlassian.netJira Cloud site. - Preserve the existing no-redirect credential protection.
Compatibility work
- Relax the current Cloud-only host validation safely for explicitly configured Server/Data Center hosts.
- Confirm the Jira REST API versions and endpoints used by issue search, priorities, worklogs, comments, attachments, and avatars against the supported Server/Data Center versions.
- Detect unsupported authentication responses and present a useful error rather than repeatedly retrying credentials.
- Add tests covering mode selection, Authorization headers, host binding, HTTPS enforcement, secret persistence, and Jira Cloud rejection.
Acceptance criteria
- A user can connect to a supported Jira Server/Data Center instance using a username and password.
- Existing scoped and classic Jira Cloud API-token connections continue to work unchanged.
- Account passwords are not offered as a working Jira Cloud authentication method.
- Credentials are never written to settings, logs, command-line arguments, or telemetry in plaintext.
- Automated tests cover both the new authentication mode and regression behaviour for current Cloud authentication.
Security note
Username/password Basic authentication is less desirable than OAuth, SSO, or a limited-scope token and may bypass some interactive MFA controls. The UI should describe it as a compatibility option for managed Jira Server/Data Center environments rather than the recommended default.
- Dominant language
- C#
- Stars
- 0
- Forks
- 0
- Avg merge
- 6h 29m
- Merged PRs (30d)
- 18
Getting set up
This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from GDMTT/JiraTaskBar
-
About screenOpenenhancement
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
GDMTT/JiraTaskBar#45 · 2 comments ·
Maintainers usually reply within 1 day
-
bug good first issue
Difficulty 2/5 1-3 hours Newbie friendliness 67/100
GDMTT/JiraTaskBar#22 ·
Maintainers usually reply within 1 day
-
documentation enhancement
Difficulty 4/5 3-5 days Newbie friendliness 35/100
GDMTT/JiraTaskBar#44 ·
Maintainers usually reply within 1 day
-
Calendar ViewOpenenhancement
Difficulty 5/5 Over a week Newbie friendliness 35/100
GDMTT/JiraTaskBar#43 · 4 comments ·
Maintainers usually reply within 1 day
-
enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 55/100
GDMTT/JiraTaskBar#42 · 2 comments ·
Maintainers usually reply within 1 day
All issues in GDMTT/JiraTaskBar
Similar issues
-
needs triage
Difficulty 1/5 Under an hour Newbie friendliness 71/100
Maintainers usually reply within 1 day
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 66/100
majorsilence/Majorsilence.Forms#718 ·
Maintainers usually reply within 1 day
-
bug debugger flaky small
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
Maintainers usually reply within 1 day
-
[BUG] MyAnonaMouse search turns a curly apostrophe into a space, so titles with ’ are never foundOpen
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
Maintainers usually reply within 1 day
-
documentation
Difficulty 1/5 Under an hour Newbie friendliness 90/100
Maintainers usually reply within 1 day