A critical vulnerability was discovered in React Server Components (Next.js). Our systems remain protected but we advise to update packages to newest version. Learn More. 

AI OnAI Off

Content Deliver API - auth/token returns 400 - Bad Request

David Lewis
David Lewis
Vote:
 

Setting up the API and am having issues with the auth/token request.  I have the services up and running and with out auth I can pull data as expected but, if I try hitting the auth/token path I receive a 400 - Bad Request error. No errors are being logged.

  • ContentApiRead role has been created an mapped to the Root content item\
Here are the post request that is being sent over (username and password XXX'd out)
Request:
POST /api/episerver/auth/token HTTP/1.1
Accept: application/json
Accept-Language: en
Content-Type: application/x-www-form-urlencoded
Cookie: ARRAffinity=b43e80ef1fbcb9f9d446cbc61b366e02dafefc2a9addab525b1fc3eda44b27b2; ARRAffinitySameSite=b43e80ef1fbcb9f9d446cbc61b366e02dafefc2a9addab525b1fc3eda44b27b2; TiPMix=34.5594915722308; x-ms-routing-name=self
 
grant_type=password&username=XXXX&password=XXXXXX&client_id=Default
 
HTTP/1.1 400 Bad Request
Server: cloudflare
Date: Mon, 19 Jul 2021 18:49:35 GMT
Content-Type: text/html
Content-Length: 155
Connection: close
CF-RAY: -
 
Response:
<html>
<head><title>400 Bad Request</title></head>
<body>
<center><h1>400 Bad Request</h1></center>
<hr><center>cloudflare</center>
</body>
</html>

 

#259135
Jul 19, 2021 19:26
* You are NOT allowed to include any hyperlinks in the post because your account hasn't associated to your company. User profile should be updated.