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

Don't store generated one-shot client certificates #18587

Closed
kroepke opened this issue Mar 12, 2024 · 1 comment · Fixed by #19180
Closed

Don't store generated one-shot client certificates #18587

kroepke opened this issue Mar 12, 2024 · 1 comment · Fixed by #19180
Assignees

Comments

@kroepke
Copy link
Member

kroepke commented Mar 12, 2024

As discussed in #18522 (comment), we currently store generated client certificates in a secure location on the local file system with other CA/PKI-related files.

As that is node-local, that file is not necessarily available for requests to be read in a cluster.
In this case, we only intend for a user to download this certificate with third-party clients, e.g., curl, dashboards like Grafana, or other custom applications requiring direct OpenSearch access.
Arguably, we don't need to store this particular certificate at all.

@todvora
Copy link
Contributor

todvora commented Apr 30, 2024

The actual file was needed just for the certificate signing process. We we able replace it with an in-memory implementation that doesn't store anything in the FS while keeping the very same functionality.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants