JiraError HTTP 403: Basic auth with password is not allowed

[dedarritchon]

Atlassian has deprecated the ability to use plaintext passwords with basic auth. You need to update the tool to use basic authentication with an API token, OAuth, or Atlassian Connect:

https://developer.atlassian.com/cloud/jira/platform/deprecation-notice-basic-auth-and-cookie-based-auth/?_ga=2.46857255.1839331505.1580734130-1542450647.1578313476

Is there a way to still use the tool? Thanks

[optilude]

Good question. It would likely need a code change and it depends on whether the underlying jira python library supports it. Hopefully isn’t a difficult change but will need some investigating.

---

Martin Aspeli Partner | Deloitte Digital +44 07989 304475

---

From: dedarritchon notifications@github.com Sent: Tuesday, February 4, 2020 1:52:54 PM To: DeloitteDigitalUK/jira-agile-metrics jira-agile-metrics@noreply.github.com Cc: Subscribed subscribed@noreply.github.com Subject: [EXT: NEWSLETTER] [DeloitteDigitalUK/jira-agile-metrics] JiraError HTTP 403: Basic auth with password is not allowed (#18)

Atlassian has deprecated the ability to use plaintext passwords with basic auth. You need to update the tool to use basic authentication with an API token, OAuth, or Atlassian Connect:

https://developer.atlassian.com/cloud/jira/platform/deprecation-notice-basic-auth-and-cookie-based-auth/?_ga=2.46857255.1839331505.1580734130-1542450647.1578313476

Is there a way to still use the tool? Thanks

— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHubhttps://github.com/DeloitteDigitalUK/jira-agile-metrics/issues/18?email_source=notifications&email_token=AABHJCUYG77BPGJO7WLXTY3RBFXLNA5CNFSM4KPXJKKKYY3PNVWWK3TUL52HS4DFUVEXG43VMWVGG33NNVSW45C7NFSM4IK43SFA, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AABHJCQEVHXTYUVSUJQTPC3RBFXLNANCNFSM4KPXJKKA. IMPORTANT NOTICE

This communication is from Deloitte LLP, a limited liability partnership registered in England and Wales with registered number OC303675. Its registered office is 1 New Street Square, London EC4A 3HQ, United Kingdom. Deloitte LLP is the United Kingdom affiliate of Deloitte NSE LLP, a member firm of Deloitte Touche Tohmatsu Limited, a UK private company limited by guarantee (“DTTL”). DTTL and each of its member firms are legally separate and independent entities. DTTL and Deloitte NSE LLP do not provide services to clients. Please see www.deloitte.co.uk/abouthttps://www.deloitte.co.uk/about to learn more about our global network of member firms. For details of our professional regulation please see Regulatorshttps://www2.deloitte.com/uk/en/footerlinks1/regulators-and-provision-service-regulations.html.

This communication contains information which is confidential and may also be privileged. It is for the exclusive use of the intended recipient(s). If you are not the intended recipient(s), please notify it.security.uk@deloitte.co.ukmailto:it.security.uk@deloitte.co.uk and destroy this message immediately. Email communications cannot be guaranteed to be secure or free from error or viruses. All emails sent to or from a @deloitte.co.uk email account are securely archived and stored by an external supplier within the European Union.

You can understand more about how we collect and use (process) your personal information in our Privacy Noticehttps://www2.deloitte.com/uk/en/legal/privacy.html.

Deloitte LLP does not accept any liability for use of or reliance on the contents of this email by any person save by the intended recipient(s) to the extent agreed in a Deloitte LLP engagement contract.

Opinions, conclusions and other information in this email which have not been delivered by way of the business of Deloitte LLP are neither given nor endorsed by it.

[joska]

Although strange, the quick workaround for this issue seems to be using the Username with API token as a password. You can generate API token on https://id.atlassian.com/manage/api-tokens

[lauter-bach]

Can anyone confirm that this workaround is still working ? --username < jira-username > --password < jira-token > ist not working in my case. Get 403 - Forbidden.

README.md states that this should be possible: "Generate an API token for your user in JIRA settings and use this API token instead of password in your scripts"

Also tried Username: < jira-username > Password: < jira-tocken > within 'Connection' section in yaml file.

thanks for any help in advance

[maqqju]

I am having the same issue - and realized that the problem is that for some JIRA versions Basic Auth with an API Token does not work. Instead, you will need to use a Bearer authentication.

I tried to fork out and use JWT, which did not do the job.

Do you have any ideas on how to go about it?