[[["์ดํดํ๊ธฐ ์ฌ์","easyToUnderstand","thumb-up"],["๋ฌธ์ ๊ฐ ํด๊ฒฐ๋จ","solvedMyProblem","thumb-up"],["๊ธฐํ","otherUp","thumb-up"]],[["์ดํดํ๊ธฐ ์ด๋ ค์","hardToUnderstand","thumb-down"],["์๋ชป๋ ์ ๋ณด ๋๋ ์ํ ์ฝ๋","incorrectInformationOrSampleCode","thumb-down"],["ํ์ํ ์ ๋ณด/์ํ์ด ์์","missingTheInformationSamplesINeed","thumb-down"],["๋ฒ์ญ ๋ฌธ์ ","translationIssue","thumb-down"],["๊ธฐํ","otherDown","thumb-down"]],["์ต์ข ์ ๋ฐ์ดํธ: 2025-08-30(UTC)"],[[["\u003cp\u003eThe provided content details the creation of self-signed TLS certificates for trial or testing purposes within the Apigee hybrid environment.\u003c/p\u003e\n"],["\u003cp\u003eSelf-signed certificates are explicitly not recommended for production environments and should only be considered for development, trial, or testing.\u003c/p\u003e\n"],["\u003cp\u003eThe runtime ingress gateway requires a TLS certificate/key pair, which can be self-signed for quickstart installations using the \u003ccode\u003eopenssl\u003c/code\u003e utility.\u003c/p\u003e\n"],["\u003cp\u003eA specific command using \u003ccode\u003eopenssl\u003c/code\u003e is provided to generate the self-signed certificate and key pair, storing them in a designated \u003ccode\u003ecerts\u003c/code\u003e directory, while setting the CN parameter to any desired value.\u003c/p\u003e\n"],["\u003cp\u003eThe resulting files, \u003ccode\u003ekeystore.pem\u003c/code\u003e (certificate) and \u003ccode\u003ekeystore.key\u003c/code\u003e (key), should be located within the \u003ccode\u003e./certs\u003c/code\u003e directory after running the provided command.\u003c/p\u003e\n"]]],[],null,["# Generate self-signed TLS credentials\n\n| You are currently viewing version 1.4 of the Apigee hybrid documentation. **This version is end of life.** You should upgrade to a newer version. For more information, see [Supported versions](/apigee/docs/hybrid/supported-platforms#supported-versions).\n\n\nThis topic explains how to create self-signed TLS certificates for use in an\nenvironment configuration. This information is intended for trial or testing\npurposes only.\n| **Warning:** Self-signed certificates are not recommended for production. Only consider using them for development, trial, or testing purposes.\n\n\nThe runtime ingress gateway (the gateway that handles API proxy traffic) requires\na TLS certificate/key pair. For this quickstart installation, you can use self-signed\ncredentials. In the following steps, [openssl](https://www.openssl.org/) is used\nto generate the credentials.\n\n1. Be sure that you are in the \u003cvar translate=\"no\"\u003ebase_directory\u003c/var\u003e`/hybrid-files` directory. It was suggested in the installation quickstart that you create a `hybrid-files` directory to contain files that you create. Your file structure may differ from the suggested structure.\n2. Execute the following command from inside `hybrid-files` directory, where `./certs` is the directory containing your certificates. \n\n ```\n openssl req -nodes -new -x509 -keyout ./certs/keystore.key -out \\\n ./certs/keystore.pem -subj '/CN=mydomain.net' -days 3650\n ```\n\n\n This command creates a self-signed certificate/key pair that you can use for the\n quickstart installation. The CN `mydomain.net` can be any value you wish for\n the self-signed credentials.\n3. Check to make sure the files are in the `./certs` directory: \n\n ls ./certs\n keystore.pem\n keystore.key\n\n\n Where `keystore.pem` is the self-signed TLS certificate file and `keystore.key`\n is the key file."]]
