-
Notifications
You must be signed in to change notification settings - Fork 25.2k
Monitoring Exporter attempts to read closed SecureSettings #30344
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
Labels
:Data Management/Monitoring
:Security/Authentication
Logging in, Usernames/passwords, Realms (Native/LDAP/AD/SAML/PKI/etc)
Comments
@tvernum I moved it here :) |
Pinging @elastic/es-core-infra |
Pinging @elastic/es-security |
The only workaround that I'm aware of is to not use secure settings with monitoring. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
:Data Management/Monitoring
:Security/Authentication
Logging in, Usernames/passwords, Realms (Native/LDAP/AD/SAML/PKI/etc)
Using 6.2.3 and secure monitoring settings below causes bootstrap errors below:
Keystore settings:
Is there any workaround?
Related to: https://github.com/elastic/x-pack-elasticsearch/issues/3950
The text was updated successfully, but these errors were encountered: