Forums

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

API status 200 but with empty body when using HTTP Basic Auth

Wang ZY
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!
July 12, 2019

 

A confusing problem when using Confluence REST API / SOAP api /json-rpc api :

when i send a request to a confluence api using http basic authentication , i got http status 200 but with no repsonse body, 

for example, using curl on confluence server and call ../rest/api/accessmode API  for testing , i got some response when using no auth but an empty response body when using HTTP Basic Auth :

 

 

curl -i http://localhost:8090/rest/api/accessmode

HTTP/1.1 200 
X-ASEN: SEN-L13792150
Set-Cookie: JSESSIONID=FC801E48AD3BA0A7207D80D10A94D726; Path=/; Secure; HttpOnly
Cache-Control: no-cache, must-revalidate
Expires: Thu, 01 Jan 1970 00:00:00 GMT
X-Content-Type-Options: nosniff
Content-Type: application/json
Transfer-Encoding: chunked
Date: Fri, 12 Jul 2019 10:35:25 GMT

"READ_WRITE"

 

curl -i -u admin:passwd http://localhost:8090/rest/api/accessmode

 

HTTP/1.1 200 
X-ASEN: SEN-L13792150
Set-Cookie: JSESSIONID=78A33380D09EFC4511DA4162AD2CD801; Path=/; Secure; HttpOnly
Content-Length: 0
Date: Fri, 12 Jul 2019 10:37:12 GMT

 

 

same thing happens when using SOAP or json-rpc API.

 

In addtion,  we are using Seraph and a customised Authenticator for Single Sing-on and it works well  , is that a possible cause?

 

or which log should i view to help me solve the problem?

 

---------

Confluence server version : 6.15.4

1 answer

0 votes
Thomas Deiler
Community Champion
July 14, 2019

Dear @Wang ZY ,

I tried to reproduce what you described. With Confluence 6.15.6. all curl commands worked as expected. Regardless if taking an admin or non-admin account.

Have you already tried with a REST client?

So long

Thomas

Suggest an answer

Log in or Sign up to answer
TAGS
AUG Leaders

Atlassian Community Events