Im using Qlik Sense server
JIRA is the cloud version
If i use the url in my browser it returns data
https://xxxxxx.atlassian.net/rest/api/latest/search
If i use the google chrome extension shown in attachment jira 2.png all i enter is Hostname , email address and token ID it returns data
If i try connecting via Qlik sense i get the error shown in attachment 1 which is HHTP protocol error 407 (Proxy authentication required )
Access denied (Authentication_failed)
I tried adding a query header
name Proxy-Authorization
value Basic email_adress:token_id in base64 string format
I tried basic authentication with my email address and token id also
Im not using a web connector
I checked chrome http header it seems to be using a cookie to authenticate
I have my domain\username and password to logon to pc
I have a email address to logon to cloud JIRA while on company vpn
we do have a proxy
any ideas ? im willing to try anything just to authenticate
Hi Yusuf,
I understand that you are trying to make a REST API call to Jira Cloud via Qlik Sense. Atlassian deprecated the use of cookie and password based method when using basic auth back last year. We documented this change in Deprecation notice - Basic authentication with passwords and cookie-based authentication.
So while you can reach that address in your browser, I suspect that this is happening because your browser has a current session here. I have not used Qlik Sense, but being a separate application it won't be able to use just a clear password, a cookie, or just the API token by itself. You are correct that you need to create a string of emailaddress:APItoken and then base64 encode that string. But there are some specific headers that have to be included in the call for this to work.
Check out our Basic auth for REST APIs. You do need an authorization header, but it will look more like this:
"Authorization: Basic ZnJlZDpmcmVk"
and not
"Proxy-Authorization Basic ZnJlZDpmcmVk"
You are also going to need to specify the HTTP verb you want to use here (GET, PUT, POST are most common), and you'll need to also use the appropriate content type header depending on the call. To reference that endpoint it can accept either a GET or POST, there is a note that if the JQL expression is large to use the POST instead.
I'm not sure exactly how Qlik Sense works here, so perhaps it can be configured to make these REST API calls in a manner that Jira cloud would support. However I'm not positive that it supports the adjustments you would need here in order to make these calls from that application.
I hope this helps.
Andy
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.