I’m having trouble getting the Cloud /api/v2/access/validate_token endpoint to work. If I send the GET request with a newly created token in the Authorization: Bearer <my_token> header I get a 400 Bad request error with the body only having the text “BAD REQUEST”. However, when I enter random text string, for example, “asdasdad” as the token in the header I get a proper 401 Unauthorized response with a json body with the “error” key having a value of “invalid_client” which is what you would expect if a token is invalid.
The endpoint works fine on our cnMaestro on-premise. The issue is only in the Cloud version.
Anyone else having this issue?