Tweet
Hi there,
I'm trying to do something in my Espo, but an issue blocks me completely.
I have multiple API routes that are basically webhooks that are called by a 3rd party provider.
I'm using custom defined routes (Resources/routes.json).
The webhooks are providing a header named "Authorization" that gives a custom attributes that I need to process the request of these webhooks.
But, from what I saw from Espo's (Core) routing and .htaccess, the "Authorization" is already used for Espo's API.
So, I though I could just use the "noAuth" param from the routes.json file but again, this parameter is there to say that the auth is not required but still processed if given.
My issue is that Espo considers these webhooks calls as standard API calls with a Basic Authentication (and ultimately, returns a 401 error).
How could I bypass this ?
Thanks in advance.
Regards,
Firyo.
I'm trying to do something in my Espo, but an issue blocks me completely.
I have multiple API routes that are basically webhooks that are called by a 3rd party provider.
I'm using custom defined routes (Resources/routes.json).
The webhooks are providing a header named "Authorization" that gives a custom attributes that I need to process the request of these webhooks.
But, from what I saw from Espo's (Core) routing and .htaccess, the "Authorization" is already used for Espo's API.
So, I though I could just use the "noAuth" param from the routes.json file but again, this parameter is there to say that the auth is not required but still processed if given.
My issue is that Espo considers these webhooks calls as standard API calls with a Basic Authentication (and ultimately, returns a 401 error).
How could I bypass this ?
Thanks in advance.
Regards,
Firyo.
Comment