How Qlik JIRA connector is affected by the depreciation of basic authentication in JIRA

JIRA connector fails with:

Failed on attempt 1 to GET (The remote server returned an error: (401) Unauthorized.)

Atlassian announced in the following public article https://developer.atlassian.com/cloud/jira/platform/deprecation-notice-basic-auth-and-cookie-based-auth/ that basic authentication (username-password) and cookie-based authentication is depreciated. From 3rd June 2019, connections to REST endpoint in JIRA or Confluence Cloud have use an API token, OAuth, or Atlassian Connect.

Documentation of Atlassian Cloud API token: https://confluence.atlassian.com/cloud/api-tokens-938839638.html?utm_source=alert-email&utm_medium=email&utm_campaign=jira-conf-api-auth-vs-tokens_EML-4935&jobid=104098709&subid=1405894709

How does this change affect Qlik Web Connectors?

As confirmed by R&D, this would be the authentication step in Qlik Web Connectors in accordance with the change from JIRA: 

• For JIRA Server: use username & password (this is not affected by the change of authentication above). 
• For JIRA Cloud: use email address in the username field and API token in the password field. 

On Qlik Web Connectors November 2018 or earlier, you might get error "Username did not match". If this happens, the solution would be upgrading to Qlik Web Connectors May 2019.

Environment:

• Qlik Web Connectors up to version May 2019