Este tópico explica como criar certificados TLS autoassinados para uso em uma
configuração de ambiente. Essas informações são apenas para fins de avaliação
ou teste.
O gateway de entrada de ambiente de execução (o gateway que processa o tráfego de proxy da API) exige
um par de certificado/chave TLS. Para esta instalação do guia de início rápido, use credenciais
autoassinadas. Nas etapas a seguir, o openssl é usado
para gerar as credenciais.
Execute o comando a seguir para criar os arquivos de certificado e de chave. Os arquivos de certificado
provavelmente terão as extensões .crt ou .pem e o arquivo de chave provavelmente
terá .key.
Esse comando cria um par de certificado/chave autoassinados que você pode usar para a
instalação do guia de início rápido. O CN mydomain.net pode ser qualquer valor pretendido para
as credenciais autoassinadas.
Verifique se os arquivos estão no diretório ./certs:
ls ./certs
keystore.pem
keystore.key
Em que keystore.pem é o arquivo de certificado TLS autoassinado e keystore.key
é o arquivo de chave.
[[["Fácil de entender","easyToUnderstand","thumb-up"],["Meu problema foi resolvido","solvedMyProblem","thumb-up"],["Outro","otherUp","thumb-up"]],[["Difícil de entender","hardToUnderstand","thumb-down"],["Informações incorretas ou exemplo de código","incorrectInformationOrSampleCode","thumb-down"],["Não contém as informações/amostras de que eu preciso","missingTheInformationSamplesINeed","thumb-down"],["Problema na tradução","translationIssue","thumb-down"],["Outro","otherDown","thumb-down"]],["Última atualização 2025-08-28 UTC."],[[["\u003cp\u003eThis document explains how to create self-signed TLS certificates for trial or testing environments, which are not recommended for production use.\u003c/p\u003e\n"],["\u003cp\u003eThe runtime ingress gateway requires a TLS certificate/key pair, and self-signed credentials can be used for quickstart installations.\u003c/p\u003e\n"],["\u003cp\u003eThe \u003ccode\u003eopenssl\u003c/code\u003e command is used to generate self-signed certificate and key files, which should preferably be stored in the \u003ccode\u003ehybrid-files/certs\u003c/code\u003e directory if using \u003ccode\u003eapigeectl\u003c/code\u003e.\u003c/p\u003e\n"],["\u003cp\u003eA sample \u003ccode\u003eopenssl\u003c/code\u003e command is provided to generate the certificate/key pair, with the ability to customize the Common Name (CN) value, and it will create two files, \u003ccode\u003ekeystore.pem\u003c/code\u003e (certificate) and \u003ccode\u003ekeystore.key\u003c/code\u003e (key).\u003c/p\u003e\n"]]],[],null,["# Generate self-signed TLS credentials\n\n| You are currently viewing version 1.11 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\n 1. Execute the following command to create the certificate and key files. The certificate files will most likely have `.crt` or `.pem` extensions and the key file will most likely have `.key`. **Note:** If you are using `apigeectl` to install and manage Apigee hybrid, we recommend storing the certificate and key files in your \u003cvar translate=\"no\"\u003ehybrid-files\u003c/var\u003e`/certs` directory. \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.\n2. 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."]]
