OpenSearch/elasticsearch/bin/x-pack/certgen.bat

@echo off

rem Copyright Elasticsearch B.V. and/or licensed to Elasticsearch B.V. under one
rem or more contributor license agreements. Licensed under the Elastic License;
rem you may not use this file except in compliance with the Elastic License.

PUSHD "%~dp0"
CALL "%~dp0.in.bat" org.elasticsearch.xpack.ssl.CertificateTool %*
POPD
security: add tool to simplify creation of certificate and csr files This commit adds a CLI tool that can be used to generate a CA and signed certificates in PEM format. The tool only requires a name of an instance to be provided by the user; ip and dns values are supported but optional. By default, the tool is interactive and will prompt the user for input but an option exists to provide a yaml file that contains the necessary information to generate certificates or signing requests. The output is in the form of a zip file with subfolders for each instance. Neither the zip file or the PEM files are encrypted as some parts of our stack do not support encrypted PEM files. Original commit: elastic/x-pack-elasticsearch@3dc0f8d495bd73b7efce4c92ad85c410294e980b 2016-07-07 07:41:48 -04:00			`@echo off`

			`rem Copyright Elasticsearch B.V. and/or licensed to Elasticsearch B.V. under one`
			`rem or more contributor license agreements. Licensed under the Elastic License;`
			`rem you may not use this file except in compliance with the Elastic License.`

			`PUSHD "%~dp0"`
Migrate xpack to use the common ssl configuration This change migrates xpack (security, watcher, and monitoring) to use the common ssl configuration for the elastic stack. As part of this work, several aspects of how we deal with SSL has been modified. From a functionality perspective, an xpack wide configuration for SSL was added and all of the code that needs SSL uses the SSLService now. The following is a list of all of the aspects of xpack that can have their own SSL configuration, which are separate from the xpack wide configuration: * Transport * Transport profiles * HTTP Transport * Realms * Monitoring Exporters * HTTP Client In terms of the code, some cleanups were made with these changes. SSLConfiguration is now a concrete class and SSLConfiguration.Custom and SSLConfiguration.Global have been removed. The validate method on key and trust configurations has been removed and these classes will now throw exceptions when they are constructed with bad values. The OptionalSettings helper class has been removed as it was just a file with one line functions that made the code harder to understand. The SSL configuration and service classes have been moved from the security source directories to the main xpack source set. The SSLService now handles more of the configuration of the SSLEngine it returns to prevent callers from having to handle those aspects. The settings that get registered for SSL have been moved to XPackSettings. Also included in this PR is a update to the docs around SSL. This includes a large simplification to the documentation in that the certificate authority configuration section has been removed and the process that is documented for generating certificates only includes the CLI tool that we bundle. Closes elastic/elasticsearch#3104 Closes elastic/elasticsearch#2971 Closes elastic/elasticsearch#3164 Original commit: elastic/x-pack-elasticsearch@5bd9e5ef38b423dd1e1d9ea6d4d4179637b2df8b 2016-09-01 10:51:41 -04:00			`CALL "%~dp0.in.bat" org.elasticsearch.xpack.ssl.CertificateTool %*`
security: add tool to simplify creation of certificate and csr files This commit adds a CLI tool that can be used to generate a CA and signed certificates in PEM format. The tool only requires a name of an instance to be provided by the user; ip and dns values are supported but optional. By default, the tool is interactive and will prompt the user for input but an option exists to provide a yaml file that contains the necessary information to generate certificates or signing requests. The output is in the form of a zip file with subfolders for each instance. Neither the zip file or the PEM files are encrypted as some parts of our stack do not support encrypted PEM files. Original commit: elastic/x-pack-elasticsearch@3dc0f8d495bd73b7efce4c92ad85c410294e980b 2016-07-07 07:41:48 -04:00			`POPD`