You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently, the application allows registering webhooks and sends a POST request to the specified URL when triggered. However, there is no functionality to include any form of authorization with these requests. This limits the ability to securely interact with webhooks that require an API key or other authentication mechanisms.
Proposed Enhancement
Add functionality to optionally include an API key or other authorization methods (e.g., headers) when sending webhook POST requests. This will allow integration with endpoints that require secure access.
Acceptance Criteria
Users can configure an API key (or authorization token) when registering a webhook.
The API key is sent as part of the POST request headers (e.g., Authorization: Bearer ).
The functionality is optional, and the webhook should still work without an API key if not configured.
Proper validation and secure storage of the API key during webhook registration.
The text was updated successfully, but these errors were encountered:
Description
Currently, the application allows registering webhooks and sends a POST request to the specified URL when triggered. However, there is no functionality to include any form of authorization with these requests. This limits the ability to securely interact with webhooks that require an API key or other authentication mechanisms.
Proposed Enhancement
Add functionality to optionally include an API key or other authorization methods (e.g., headers) when sending webhook POST requests. This will allow integration with endpoints that require secure access.
Acceptance Criteria
The text was updated successfully, but these errors were encountered: