Your application must be configured to use the certificate, and an HTTPS endpoint must be added. Step 2: Modify the service definition and configuration files Next, you must include information about the certificate in your service definition and service configuration files. For example, the following task uses a self-signed certificate in which the common name (CN) used in the certificate is. A self-signed certificate is not authenticated through a CA and can use the domain as the website URL. The certificate must use a minimum of 2048-bit encryption.įor test purposes, you can create and use a self-signed certificate.For example, if your custom domain name is you would request a certificate from your CA for *. When you request a certificate from a CA, the certificate's subject name must match the custom domain name used to access your application. You must acquire a custom domain name to use when access your service. You cannot obtain a TLS/SSL certificate from a certificate authority (CA) for the domain. The certificate's subject name must match the domain used to access the cloud service.The certificate must be created for key exchange, exportable to a Personal Information Exchange (.pfx) file.The certificate must contain a public key.The certificate must meet the following requirements for TLS/SSL certificates in Azure: If you do not already have one, you need to obtain one from a company that sells TLS/SSL certificates. To configure TLS for an application, you first need to get a TLS/SSL certificate that has been signed by a Certificate Authority (CA), a trusted third party who issues certificates for this purpose.
Read this first if you have not yet created a cloud service. Information on using a staging deployment is provided at the end of this topic. The procedures in this task apply to Azure Cloud Services for App Services, see this.
0 kommentar(er)
