-
Notifications
You must be signed in to change notification settings - Fork 327
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Login with API token returns 401 #148
Comments
Yeah, it looks like the api tokens don't work with the |
A super hacky way to get around this is to just embed it in the basic auth for the endpoint so:
Where the %40 is the uri encoding of |
I can confirm that the work-around does work, but If I can help it I'd like to avoid leaving my API key in the config text file for the expected reasons. I'd offer to put in the work to make the change myself, but I have 0 experience with go so would probably be an empty offer : / |
Yeah, that is an insecure gross hack, I am trying to come up with something better, but will probably take a few days. |
I do have some code for this working but I am trying to sort out integration test issues now (api keys for go-jira.atlassian.net dont seem to work for my test users, not sure why yet). -Cory |
This should work now. I have updated the docs for how to use api-tokens: |
Horray! Thanks! |
Using API token since I otherwise have 2FA enabled, and it does not appear to work.
Same credentials do work via jira-cmd.js project.
(Have tried normal password and also doesn't work)
The text was updated successfully, but these errors were encountered: