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.

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

Alerting docs to have some mention about key rotation #74781

Closed
mikecote opened this issue Aug 11, 2020 · 4 comments
Closed

Alerting docs to have some mention about key rotation #74781

mikecote opened this issue Aug 11, 2020 · 4 comments
Assignees
Labels
Feature:Actions Feature:Alerting Team:ResponseOps Label for the ResponseOps team (formerly the Cases and Alerting teams)

Comments

@mikecote
Copy link
Contributor

Ex: mention what needs to be done, the impacts of not keeping the old key, etc.

Key rotation feature is tracked under: #56889.

@mikecote mikecote added Feature:Alerting Feature:Actions Team:ResponseOps Label for the ResponseOps team (formerly the Cases and Alerting teams) labels Aug 11, 2020
@elasticmachine
Copy link
Contributor

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

@mikecote mikecote mentioned this issue Aug 19, 2020
36 tasks
@mikecote
Copy link
Contributor Author

mikecote commented Oct 2, 2020

Removing blocked label now that the feature is merged #72420.

@mikecote
Copy link
Contributor Author

@bmcconaghy, @azasypkin just mentioned the official documentation about key rotation is now up: https://www.elastic.co/guide/en/kibana/7.10/xpack-security-secure-saved-objects.html. We can reference it from our mention.

@bmcconaghy
Copy link
Contributor

Addressed by #84529

@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
Labels
Feature:Actions Feature:Alerting Team:ResponseOps Label for the ResponseOps team (formerly the Cases and Alerting teams)
Projects
None yet
Development

No branches or pull requests

4 participants