-
Notifications
You must be signed in to change notification settings - Fork 2.4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Ability to require a specific header to accept incoming webhook. #24270
Labels
Comments
greatestusername
added
enhancement
New feature or request
needs triage
New item requiring triage
labels
Jul 14, 2023
Pinging code owners: See Adding Labels via Comments if you do not have permissions to add labels yourself. |
I would be more than happy to sponsor this |
dmitryax
pushed a commit
that referenced
this issue
Aug 3, 2023
**Description:** Adding a feature - Allow option of adding a required header for incoming webhook requests. If header doesn't match, returns a 401. **Link to tracking Issue:** [<24270>](#24270)
I believe the work here is complete, thanks @greatestusername ! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Component(s)
receiver/webhookevent
Is your feature request related to a problem? Please describe.
Use Case:
Many webhooks send along an HTTP header to pass a secret/token. For example GitLab uses the token
X-GitLab-Token
.Describe the solution you'd like
Allow an optional config setting in the webhook receiver to add a header that must be matched before accepting the incoming connection.
Essentially a config like:
Any requests to the webhook receiver that do not have that required header would be returned a 401
Describe alternatives you've considered
Possible some integrations would want to send a token in the query param but headers is most common.
Additional context
No response
The text was updated successfully, but these errors were encountered: