Forums

Articles
Create
cancel
Showing results for 
Search instead for 
Did you mean: 

Empty list when getting info using Basic Auth with "JSM Customers"

Carlos A_ López Ortín April 25, 2022

Hello, experts:

I'm making a web page that need to load some info from Jira Cloud. The Web is in .NET Core.

When I try with my user, I can get the info OK. But if I connect with a "customer account" (also called JSM Customer), I get a 200 response, but no info at all.

I tried with Postman, adding the API Token, as Basic header, created using this two tutorials:
https://developer.atlassian.com/cloud/jira/platform/basic-auth-for-rest-apis/
https://support.atlassian.com/atlassian-account/docs/manage-api-tokens-for-your-atlassian-account/
But the JSON is like:

[code]{
"startAt": 0,
"maxResults": 50,
"total": 0,
"issues": []
}[/code]

So, reading this post:
https://community.atlassian.com/t5/Jira-Software-questions/user-search-API-returning-empty-list/qaq-p/1345440

I opened GIT Bash and added this command:

[code]curl -u "example@mail.com:***********************" -D- -X GET "https://myname.atlassian.net/rest/api/3/search?fields=project,summary,reporter,issuetype,created,status&&maxResults=1000" > log.txt[/code]

I got this on the console:

[code] % Total % Received % Xferd Average Speed Time Time Time Current
Dload Upload Total Spent Left Speed
100 52 0 52 0 0 52 0 --:--:-- 0:00:01 --:--:-- 38[/code]

It looks like it got about 52 issues data, but in the log.txt i have this:

[code]

HTTP/2 200
server: AtlassianProxy/1.19.3.1
vary: Accept-Encoding
cache-control: no-cache, no-store, no-transform
content-type: application/json;charset=UTF-8
strict-transport-security: max-age=315360000; includeSubDomains; preload
date: Mon, 25 Apr 2022 10:00:11 GMT
atl-traceid: bf86ea0d3d57dc6e
x-arequestid: 48449dc3-bb81-4dc7-a2c5-fb0223c3ad55
x-xss-protection: 1; mode=block
timing-allow-origin: *
x-envoy-upstream-service-time: 106
x-content-type-options: nosniff
set-cookie: atlassian.xsrf.token=B0OF-PAG0-T8HT-7XKW_513934a8be0d5fbe05371533d41f0ff35d7cd6f1_lout; path=/; SameSite=None; Secure
expect-ct: report-uri="https://web-security-reports.services.atlassian.com/expect-ct-report/global-proxy", enforce, max-age=86400

{"startAt":0,"maxResults":100,"total":0,"issues":[]}[/code]

So, again, no info at all.

What am I doing wrong?

 

NOTE: At first, I tried with OAUTH2, but "JSM Customers" can't log in with this method yet.

1 answer

0 votes
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
May 15, 2022

hey i experience it, too.

Suggest an answer

Log in or Sign up to answer