File tree Expand file tree Collapse file tree 1 file changed +18
-5
lines changed Expand file tree Collapse file tree 1 file changed +18
-5
lines changed Original file line number Diff line number Diff line change @@ -275,11 +275,24 @@ does not exist, it will generate the following certificates in ``{{ kayobe_env_c
275275 * root-ca.key root-ca.pem
276276
277277
278- It is also possible to use externally generated certificates for wazuh-dashboard. root-ca.pem should contain the CA chain.
279- Those certificates can be placed in ``{{ kayobe_env_config_path }}/wazuh/wazuh-certificates ``. Certificates should have the
280- same name scheme as those generated by wazuh (typicaly <node-name>.pem)
281- The key for the external certificate should be in PKCS#8 format
282- (in its header it may have BEGIN PRIVATE KEY instead of BEGIN RSA PRIVATE KEY or BEGIN OPENSSH PRIVATE KEY).
278+ It is also possible to use externally generated certificates for
279+ wazuh-dashboard. Customise the ``dashboard_node_name `` variable so that you can
280+ use a separate certificate and key for this service e.g:
281+
282+ .. code-block :: yaml
283+ :caption : $KAYOBE_CONFIG_PATH/inventory/group_vars/wazuh-manager/wazuh-manager
284+
285+ dashboard_node_name : " wazuh-dashboard"
286+
287+ You will need to create two files matching the following pattern:
288+
289+ - ``{{ dashboard_node_name }}-key.pem `` for the private key
290+ - ``{{ dashboard_node_name }}.pem `` for the certificate
291+
292+ Drop these files into ``$KAYOBE_CONFIG_PATH/environments/<environment>/wazuh/wazuh-certificates/ `` if
293+ using the kayobe environments feature, or ``$KAYOBE_CONFIG_PATH/wazuh/wazuh-certificates/ `` if not.
294+ The key for the external certificate should be in PKCS#8 format (in its header it may have BEGIN
295+ PRIVATE KEY instead of BEGIN RSA PRIVATE KEY or BEGIN OPENSSH PRIVATE KEY).
283296
284297Example OpenSSL rune to convert to PKCS#8:
285298
You can’t perform that action at this time.
0 commit comments