Jump to content

Edit History

vanessa_adabra

vanessa_adabra

Hi, I am debugging a developer for a module that's being used on Prestashop.

I have come across the following issue: for a reason I have not found my end-client token requires effective login (email and password) if I try to access this endpoint /api/SOMETHING. Meanwhile the token I have generated in my testing shop does not. For this reason, my token works when doing this request from PostMan https://TOKEN@SHOP-URL/api  but my en-client's token does not.

The solution I have found is using the ws_key=TOKEN. This works for both tokens when I send this request http://SHOP-URL/api/?ws_key=TOKEN.

My questions are: Why does this happen? And, is the ws_key a deprecated property?

 

vanessa_adabra

vanessa_adabra

Hi, I am debugging the token of the end-client whom installed my module on their shop.

The issue is that the token seems to be unauthorized and even when I use the following endpoint: https://TOKEN@SHOP-URL/api the body I get returned only this (see screenshot).

When I do the same test with my own store where I installed my module the endpoint works well.

The only difference I have found so far is that when I point the same endpoint from browser  mine does not require a username and password, but my client one does.

I have tried to replicate the issue but unsuccessfully. Have ever experienced something like this?

Schermata 2022-08-30 alle 09.16.09.png

vanessa_adabra

vanessa_adabra

Hi, I am debugging the token of the end-client whom installed my module on their shop.

The issue is that the token seems to be unauthorized and even when I use the following endpoint: https://TOKEN@SHOP-URL/api the body I get returned only this (see screenshot).

I have tried to replicate the issue but unsuccessfully. Have ever experienced something like this?

Schermata 2022-08-30 alle 09.16.09.png

×
×
  • Create New...