Hello, experts:
I wrote this in the comunity forum, then I realized that there is a developer forum. Sorry ^^U
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 from support mails), I get a 200 response, but no info at all.
I tried with Postman, adding the encoded API Token, as Basic header, created using this two tutorials:
https://developer.atlassian.com/cloud/jira/platform/basic-auth-for-rest-apis/
But the JSON is like:
{
"startAt": 0,
"maxResults": 50,
"total": 0,
"issues": []
}
So, reading this post:
I opened GIT Bash and wrote this command:
curl -u "example@mail.com:*******API-Token*******" -D- -X GET "https://myname.atlassian.net/rest/api/3/search?fields=project,summary,reporter,issuetype,created,status&maxResults=1000" > log.txt
I got this on the console:
% 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
It looks like it got 52 bytes of data, but in the log.txt I have this:
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":[]}
So, again, no info at all. The 52 bytes of data are the 52 characters on the last line.
What am I doing wrong?
NOTE: At first, I tried with OAUTH2, but “JSM Customers” can’t log in with this method yet.