We generate certificates that are intended to be used for server authentication in a couple of places:

- `bin/elasticsearch-certutil http` command  ( See `CertGenUtils.generateSignedCertificate` in `HttpCertificateCommand` )
- TLS auto-configuraion for node startup ( see [`AutoConfigureNode`](https://github.com/elastic/elasticsearch/blob/814f7f9f52cb8c05db6465b9bfc818ea5d76c575/x-pack/plugin/security/cli/src/main/java/org/elasticsearch/xpack/security/cli/AutoConfigureNode.java#L454) )

In these cases we know that the certificate is meant to be used for server authentication, so we can set Extended Key Usage extension to `1.3.6.1.5.5.7.3.1`
x-pack/plugin/security/cli/src/main/java/org/elasticsearch/xpack/security/cli/AutoConfigureNode.java
t.addSuppressed(ex);
            }
            try {
                
                deleteDirectory(env.configFile().resolve(TLS_GENERATED_CERTS_DIR_NAME));
            } catch (Exception ex) {
                t.addSuppressed(ex);
            }
            Path backupCertsDir = env.configFile()
                .resolve(
                    String.format(Locale.ROOT, TLS_GENERATED_CERTS_DIR_NAME + ".%d.orig", autoConfigDate.toInstant().getEpochSecond())
                );
            if (Files.exists(backupCertsDir)) {
                moveDirectory(backupCertsDir, env.configFile().resolve(TLS_GENERATED_CERTS_DIR_NAME));
            }
            throw t;
        }
        
        if (Files.exists(keystoreBackupPath)) {
            Files.delete(keystoreBackupPath);
        }
    }
    private String initialMasterNodesSettingValue(Environment environment) {
        if (NODE_NAME_SETTING.exists(environment.settings())) {
            return "[\"" + NODE_NAME_SETTING.get(environment.settings()) + "\"]";
        }
        return "[\"${HOSTNAME}\"]";
    }
    /**
     * Determines if a node that is enrolling to an existing cluster is on a different host than the other nodes of the