🔐 Secure your cluster with TLS, numerous authentication backends, data masking, audit logging as well as role-based access control on indices, documents, and fields
What is the bug?
After upgrading opensearch software on our server, the can't start because the democonfig installer is re-adding the security demo configuration in out working production config.
How can one reproduce the bug?
Steps to reproduce the behavior:
Install oder opensearch version
configuration plugin.security in an hierarchic style and certificates
run opensearch
apt upgrade
opensearch won't start because of missing certificates and config issues
What is the expected behavior?
It should matter if the yml configuration is writting in an hierarchic or flat style. If the configuration is valid, opensearch democonfig installer should respect set
What is the bug? After upgrading opensearch software on our server, the can't start because the democonfig installer is re-adding the security demo configuration in out working production config.
How can one reproduce the bug? Steps to reproduce the behavior:
What is the expected behavior? It should matter if the yml configuration is writting in an hierarchic or flat style. If the configuration is valid, opensearch democonfig installer should respect set
What is your host/environment?
Snippet of opensearch.yml
Do you have any additional context?
After upgrading opensearch the configuration looks like
Here is the part where democonfig looks for the existence of "plugin.security" https://github.com/opensearch-project/security/blob/main/src/main/java/org/opensearch/security/tools/democonfig/SecuritySettingsConfigurer.java#L106-L128