502 badgateway on m2m token endpoint

When I try to POST with postman to the token endpoint
https://business.kinde.com/oauth2/token
I get a 502 badgateway

It doesn't matter whether I try the correct client_id or just random chars.
I would expect to get 401 or 403 if the credentials are wrong.

Tried with this body and Content-Type: application/json

{
  "client_id": "XXX",
  "client_secret": "XXX",
  "grant_type": "client_credentials",
  "audience": "http://api.example.com/api"
}

{
  "client_id": "XXX",
  "client_secret": "XXX",
  "grant_type": "client_credentials",
  "audience": "http://api.example.com/api"
}

I do not use scope as I'm currently on the free tier, only testing out kinde.

Kinde•13mo ago•

3 replies

Drachmann

502 badgateway on m2m token endpoint

{
  "client_id": "XXX",
  "client_secret": "XXX",
  "grant_type": "client_credentials",
  "audience": "http://api.example.com/api"
}

{
  "client_id": "XXX",
  "client_secret": "XXX",
  "grant_type": "client_credentials",
  "audience": "http://api.example.com/api"
}

I do not use scope as I'm currently on the free tier, only testing out kinde.

502 badgateway on m2m token endpoint

Similar Threads

502 badgateway on m2m token endpoint

Similar Threads

Similar Threads

Similar Threads