Skip to content
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.

Sign up for GitHub

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

Jump to bottom

[ResponseOps][Connectors] Support Bearer token authentication on the webhook connector. #216126

Open
cnasikas opened this issue Mar 27, 2025 · 1 comment
Open

[ResponseOps][Connectors] Support Bearer token authentication on the webhook connector. #216126

cnasikas opened this issue Mar 27, 2025 · 1 comment
Labels
Feature:Actions/ConnectorTypes Issues related to specific Connector Types on the Actions Framework Team:ResponseOps Label for the ResponseOps team (formerly the Cases and Alerting teams)

Comments

@cnasikas
Copy link
Member

The webhook connector currently supports basic and SSL client authentication. We need to extend it to support Bearer token authentication.

Image

DoD

  • Users can select the Bearer token authentication mode.
  • Users can set the token on a password field called "Token" when selecting the Bearer token authentication mode.
  • The webhook connector automatically adds the Bearer {token_value} header and ignores other authentication parameters.
@cnasikas cnasikas added Feature:Actions/ConnectorTypes Issues related to specific Connector Types on the Actions Framework Team:ResponseOps Label for the ResponseOps team (formerly the Cases and Alerting teams) labels Mar 27, 2025
@elasticmachine
Copy link
Contributor

Pinging @elastic/response-ops (Team:ResponseOps)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
Feature:Actions/ConnectorTypes Issues related to specific Connector Types on the Actions Framework Team:ResponseOps Label for the ResponseOps team (formerly the Cases and Alerting teams)
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@cnasikas @elasticmachine