Start a new topic

Testing endpoint from console authenticated as User Session fails

When I am trying to test my custom endpoint in the console with the authentication option set to User Session - I enter the user credentials into the test popdown - I get this strange error:


400 BAD REQUEST -- { "error": "The Authorization header in your request is malformed. An Authorization header should contain two parts separated by a space: a type (Basic or Kinvey) and a base64-encoded auth string. Please refer to the REST Security Guide or contact support for more information." }


I get this error not on the firs attempt but on the second and all subsequent. 


Thanks



Hi Aniruddha


I just run the test in FF and the problem is still there, I am getting the same error. 


As for the information you are asking, I have already answered all of them except the screen capture of the request, so here you go.


Thanks


Hi Daniel,


Could you please test this with another browser - Firefox maybe? The reason I ask this is because this could a temporary issue with current Chrome version and I would like to eliminate that possibility.


Also, you can execute a custom endpoint from the code editor as well as API console, both part of Kinvey Console in the browser. Can you please test the endpoints with both the options?


If above tests fail, please capture following information:

  • X-Kinvey-Request-Id
  • Type of credential used (master/user)
  • Browser name and version
  • Screen capture of request
  • Auth header information from network tab of browser developer tools

This would help us isolate the error origin.


Thanks,
Wani

Hi Aniruddha


how about we set up a screen sharing session with one of your techies? 


Answers to your questions:

- the first request is successful, all subsequent fail as described

- happens on all edpoints

- only tried the latest Chrome

- I have tried this only in the Kinvey console

X-Kinvey-Request-Id - see above

 

Hi Daniel,


I have a couple of follow up questions:

  • Does this work for other custom endpoints?
  • Have you tried the same request from another browser?
  • Have you tried the same request through Kinvey API console?

If not, I would like you to try this and tell me what happens. This will help us eliminate possible problems and isolate the error faster.

Also, can you please try the request again and send me following information:
  • X-Kinvey-Request-Id
  • Type of credential used (master/user)
  • Browser name and version
  • Screen capture of request
  • Auth header information from network tab of browser developer tools

Regards,
Wani

Yes I am still experiencing the issue. 


This is from the failed request:

X-Kinvey-Request-Id:

1ad5e57a0e0a4036a3508e1080a16019

Hi,


Are you still facing this issue?


Can you try please this again and share "X-Kinvey-Request-Id" you get from the error response?



Regards,

Wani

Kinvey Support

Hi, is there any update on this? Thanks

Login or Signup to post a comment