The original problem reported here has been addressed and the REST API is working correctly. Please let us know if that’s not the case and, if you can confirm that it’s resolved, that would be appreciated.
The incident is still open because the impact on the product (outside of the REST API) is still ongoing.
Future updates will be posted on the incident report directly.
@ucchishta.sivaguru are you able to access the site at all using the UI? If the site can be accessed, then this is something different from the ongoing incident.
I just did a quick test in my site and I get the results when searching for an accountId. Are you sure that the accounId is correct?
@ccurti thanks for the tip. then I guess it’s different as I’m able to access the UI.
The user and the accountId is valid as I was able to query for it via /rest/api/user?accountId=xxx
However, when I query for the same accountid with /rest/api/search/user?cql=user.accountid=xxx or /rest/api/search/user?cql=user.accountid IN (xxx), I get statusCode:200 with empty results.
Currently, we are planning to use /rest/api/user/bulk as a replacement as that API gets us the expected results (we are fetching for multiple accountids)
Hi @ccurti@sash011, thanks for your time in looking into this. I finally figured out why /rest/api/search/user was returning 0 results for me with the help of @SadiqSatriya!
The first clue came was when I was able to search for myself with that API and that’s when we found out the other users I was looking for was lacking product access to Confluence.