Not able to access JIRA API's (Issue does not exist or you do not have permission to see it)

Question

Hi, I am unable to get the result for JIRA API using postman. It is always telling me this error "Issue does not exist or you do not have permission to see it.". It is a trail tenant of JIRA. In Posman, I tried using BasicAuth option by providing username and password (Password is the generated API Token). Also I passed manually the header for "Authorization: Basic base64encode(:)" in HTTP request but that also failed. Can someone please help.

Oscar Calaf_5ei8yi · Answer

I found that the Host header was not filled with our atlassian domain name, after fixing this value I'm getting the API results from postman without problems.

In other words, I was sending the request to our domain, so I was getting an obvious error, the method for encoding the user_mail:token using the pre-script inside postman works ok.

Oscar Calaf_5ei8yi · Answer

I'm having the same problem using a site-admin member account, I'm encoding the mail@mycompany.com:api_token_string using a pre-script in postman like this:

var token = pm.collectionVariables.get("token");var user = pm.collectionVariables.get("user");var encode = user+":"+token;
var CryptoJS = require("crypto-js")
//Encryptvar rawStr = CryptoJS.enc.Utf8.parse(encode);var base64 = CryptoJS.enc.Base64.stringify(rawStr);console.log(`Encrypted value: ${base64}`);
pm.collectionVariables.set("myEncodedAuth", base64);The variables are the mail and token strings as expected and the encoding seems to be ok according to the console.log results

Earl McCutcheon · Answer

Hello @Tanuj Gupta ,

Thanks for the additional details and the screenshots, and first up having Global administrator permissions do not necessarily mean that you can see all issues, But as you can see the issue in the Browser then this is not the case and the permissions are correct to see the issue so all is good there. but just as a reference point details on project permissions can be seen in "Manage project permissions", but on a free plan do note that permissions cannot be edited and are locked out, but you can still check the permissions which is helpful if you run into any issues during migration between a paid instance or a server instance to the free platform as there are a few scenarios where the permissions can cause a lockout as they are not editable once converted to the free plan.

The next point comes from the last screenshot where the API token "MyDevTest" is showing as "Never Accessed" which indicates that the input of this token from Postman and the attempt from the HTTP request using the BASE64 encoded username had the token fail or is not using the correct format so the token was never truly accessed.

In Postman using the username and password directly the formatting for this should not have any whitespace, either leading or trailing, check to make sure that the two fields don't have any extra spaces that may have been inadvertently copied over in front of or after the input string.

As for BASE64 encoding on the value additional details can bee seen in the following document but the format for generating this in Windows or a Linux/Unix/MacOS systems would be as follows:

* Basic auth for REST APIs

Windows:

$Text = ‘user@example.com:api_token_string’ $Bytes = [System.Text.Encoding]::UTF8.GetBytes($Text) $EncodedText = [Convert]::ToBase64String($Bytes) $EncodedText

Linux/Unix/MacOS:

echo -n user@example.com:api_token_string | base64

Also as mentioned in the KB above, you may have triggered a CAPTCHA.  Try logging out and back into your Jira instance to see if the CAPTCHA is enabled as it may have been triggered from previous formatting issues in the input strings causing multiple failed login attempts, where your current connected user session in the browser is still intact via a verified token but the subsequent Postman calls are getting blocked with the new login attempts behind a captcha.

Regards,
Earl