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

[Alerting] Expose separate from ProxySettings rejectUnauthorized configuration option. #75108

Closed
YulNaumenko opened this issue Aug 14, 2020 · 1 comment · Fixed by #76061
Closed

[Alerting] Expose separate from ProxySettings rejectUnauthorized configuration option. #75108

YulNaumenko opened this issue Aug 14, 2020 · 1 comment · Fixed by #76061
Assignees
@YulNaumenko
Labels
Feature:Alerting Team:ResponseOps Label for the ResponseOps team (formerly the Cases and Alerting teams)

Comments

@YulNaumenko
Copy link
Contributor

For configuring action executions we should have two different rejectUnauthorized servers to deal with - the proxy server, and the target server (eg, transportConfig.host/port here).

Ideally we want a rejectUnauthorized for every action type that uses http, but perhaps we can start with a simpler global config for this, see if that's good enough for customers.
@YulNaumenko YulNaumenko added Feature:Alerting Team:ResponseOps Label for the ResponseOps team (formerly the Cases and Alerting teams) labels Aug 14, 2020
@elasticmachine
Copy link
Contributor

Pinging @elastic/kibana-alerting-services (Team:Alerting Services)

@YulNaumenko YulNaumenko self-assigned this Aug 25, 2020
@YulNaumenko YulNaumenko mentioned this issue Aug 27, 2020
Merged
@kobelb kobelb added the needs-team Issues missing a team label label Jan 31, 2022
@botelastic botelastic bot removed the needs-team Issues missing a team label label Jan 31, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@YulNaumenko YulNaumenko

Labels
Feature:Alerting Team:ResponseOps Label for the ResponseOps team (formerly the Cases and Alerting teams)
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Exposed separate from ProxySettings rejectUnauthorized configuration option. YulNaumenko/kibana
3 participants
@kobelb @elasticmachine @YulNaumenko