feat(Jira Software Node): Personal Access Token credential type #11038
+92
−11
Conversation
This file contains 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
|
|
n8n-assistant
bot
added
community
|
Hey @GKdeVries, Thanks for the PR, We have created "GHC-274" as the internal reference to get this reviewed. One of us will be in touch if there are any changes needed, in most cases this is normally within a couple of weeks but it depends on the current workload of the team. |
|
Awesome. We need this feature ! |
|
Any update here? Would be greate to have this, currently stops me from investigating n8n for us as password sign in is disabled for our instance |
|
Is there any progress? Since there are more and more Jira instances of other users moving from basic auth to PAT authentication. |
netroy
approved these changes
Jan 22, 2025
netroy
changed the title
GKdeVries
changed the title
Merged
|
Got released with |
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
The company where I'm working at, is switching really soon to SSO only, this means that I can't use the basic authentication method anymore with Jira Rest calls. So I've added the Personal Access Token option to the current Jira node code.
Related Linear tickets, Github issues, and Community forum posts
I've talked about it (shortly) in the following feature request: (https://community.n8n.io/t/jira-data-center-personal-access-token-auth-type/45579).
But the timetables where shortend a lot and change to sso is already next week, so I've took this change upon myself.
Review / Merge checklist
release/backport(if the PR is an urgent fix that needs to be backported)