Basic authentication with passwords is deprecated

Hi,

I know this issue is a bit older but exploring this module. Was looking at the code for this issue, when I saw some code that maybe the dev version of the module currently already allows for this.

I can get a successful connection with Jira using the API key, using the Key module. For key name add Jira user name and then for key type select Authentication, for key value add the API key.

Then in the configuration create an endpoint. For credential provider select Key Module. Then for user name and 'password' chose the key name. It should show as autofill in the dropdown menu. Enter the url instance path, and press validate.

So, the code can handle it already, iiuc, would just need to adjust some field headings and texts that it is a bit clearer.

dan kolbas → made their first commit to this issue’s fork.

I agree that this should be updated. I just tossed together some code to help assist with this. Most of the bulk changes were done to the provider form.

WHY
I have an initiative at my work to build out a custom gitlab pipeline that will integrate JIRA_REST and atm i am leaning towards jira_updates_reporter module. So that we can automate our process for keeping our contributed modules updated with the least amount of effort.
Aka.

• Create JIRA tickets based on modules out of date based on druapl.org
• spin up containerized preview environments with an MR against our projects with the update applied.
• run our regression tests, performance tests against it and update jira accordingly.
• In turn triggering it to be passed it off to our QA team if nothing goes wrong.

Take out that developer intervention. ;)

I mention the above because the updates here and to the jira_updates_reporter are planed to be generic enough that people using this might be interested as well in it when i am done.

Just noticed i fixed the validate call, but its failing for normal calls due to additional function support needed. Patch coming soon