You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In order for the command-manager plugin to connect to the Wazuh Server's management API using self-signed certificates, a CAcert needs to be loaded into the plugin's trust chain.
We need to expose this as a setting in the configuration file.
The text was updated successfully, but these errors were encountered:
How to put configuration attributes in opensearch.yml.
The process is simple and similar to putting configurations in keystore. Depending on the type of attribute, if it is a secure configuration or not, it will automatically be saved in the keystore or in the opensearch.yml file.
Example of declaration of secure setting:
public static final Setting<SecureString> M_API_AUTH_USERNAME =
SecureSetting.secureString("m_api.auth.username", null);
Example of declaration of not secure setting:
public static final Setting<String> WAZUH_INDEXER_CA_CERT_PATH =
Setting.simpleString("ssl.http.pemtrustedcas_filepath", Setting.Property.NodeScope);
Validate configuration values.
We do not yet validate the contents of the attributes in the settings, but we will probably want to do so in the future. We can see a good example of how to create and validate settings here.
Access to files with AccessController.doPrivileged
To use the AccesController we have to configure a policy file inside plugins/command-manager/src/main/plugin-metadata/
Inside this file, if we want to manage the access to a file we cannot put a “*”, we have to put a concrete directory or an absolute path to a file.
Example. grant { permission java.io.FilePermission "/home/user/Documents/wazuh-certificates/root-ca.pem", "read";}
Description
In order for the command-manager plugin to connect to the Wazuh Server's management API using self-signed certificates, a
CAcert
needs to be loaded into the plugin's trust chain.We need to expose this as a setting in the configuration file.
The text was updated successfully, but these errors were encountered: