Important: This example is intended to provide general guidance to IT professionals who are experienced with SSL requirements and configuration. The procedure described in this article is just one of many available methods you can use to generate the required files. The process described here should be treated as an example and not as a recommendation.
Crt and key files represent both parts of a certificate, key being the private key to the certificate and crt being the signed certificate. It's only one of the ways to generate certs, another way would be having both inside a pem file or another in a p12 container. How to Generate a CSR for F5 BIG IP (version 9) The following instructions will guide you through the CSR generation process on F5 BIG-IP Loadbalancer (version 9). To learn more about CSRs and the importance of your private key, reference our Overview of Certificate Signing Request article.
When you configure Tableau Server to use Secure Sockets Layer (SSL) encryption, this helps ensure that access to the server is secure and that data sent between Tableau Server and Tableau Desktop is protected.
Looking for Tableau Server on Linux? See Example: SSL Certificate - Generate a Key and CSR.
Tableau Server uses Apache, which includes OpenSSL. You can use the OpenSSL toolkit to generate a key file and Certificate Signing Request (CSR) which can then be used to obtain a signed SSL certificate.
Steps to generate a key and CSR
To configure Tableau Server to use SSL, you must have an SSL certificate. To obtain the SSL certificate, complete the steps:
You can find additional information on the SSL FAQ page on the Apache Software Foundation website.
Configure a certificate for multiple domain names
Tableau Server allows SSL for multiple domains. To set up this environment, you need to modify the OpenSSL configuration file, openssl.conf, and configure a Subject Alternative Name (SAN) certificate on Tableau Server. See For SAN certificates: modify the OpenSSL configuration file below.
Set the OpenSSL configuration environment variable (optional)
To avoid using the
-config argument with every use of openssl.exe, you can use the OPENSSL_CONF environment variable to ensure that the correct configuration file is used and all configuration changes made in subsequent procedures in this article produce expected results (for example, you must set the environment variable to add a SAN to your certificate).
Open the Command Prompt as an administrator, and run the following command:
set OPENSSL_CONF=c:Program FilesTableauTableau Serverpackagesapache.<version_code>confopenssl.cnf
Notes:
Generate a key
Generate a key file that you will use to generate a certificate signing request.
Create a certificate signing request to send to a certificate authority
Use the key file you created in the procedure above to generate the certificate signing request (CSR). You send the CSR to a certificate authority (CA) to obtain a signed certificate.
Important: If you want to configure a SAN certificate to use SSL for multiple domains, first complete the steps in For SAN certificates: modify the OpenSSL configuration file below, and then return to here to generate a CSR.
Send the CSR to a certificate authority to obtain an SSL certificate
Send the CSR to a commercial certificate authority (CA) to request the digital certificate. For information, see the Wikipedia article Certificate authority and any related articles that help you decide which CA to use.
Use the key and certificate to configure Tableau Server
When you have both the key and the certificate from the CA, you can configure Tableau Server to use SSL. For the steps, see Configure External SSL.
For SAN certificates: modify the OpenSSL configuration file
In a standard installation of OpenSSL, some features are not enabled by default. To use SSL with multiple domain names, before you generate the CSR, complete these steps to modify the openssl.cnf file.
Additional information
If you prefer to use a different version of OpenSSL, you can download it from Open SSL for Windows.
Thanks for your feedback!There was an error submitting your feedback. Try again or send us a message.-->
Azure App Service provides a highly scalable, self-patching web hosting service. This article shows you how to create, upload, or import a private certificate or a public certificate into App Service.
Once the certificate is added to your App Service app or function app, you can secure a custom DNS name with it or use it in your application code.
The following table lists the options you have for adding certificates in App Service:
Prerequisites
To follow this how-to guide:
Private certificate requirements
Note
Azure Web Apps does not support AES256 and all pfx files should be encrypted with TripleDES.
The free App Service Managed Certificate or the App Service certificate already satisfy the requirements of App Service. If you choose to upload or import a private certificate to App Service, your certificate must meet the following requirements:
To secure a custom domain in a TLS binding, the certificate has additional requirements:
Note
Elliptic Curve Cryptography (ECC) certificates can work with App Service but are not covered by this article. Work with your certificate authority on the exact steps to create ECC certificates.
Prepare your web app
To create custom security bindings or enable client certificates for your App Service app, your App Service plan must be in the Basic, Standard, Premium, or Isolated tier. In this step, you make sure that your web app is in the supported pricing tier.
Sign in to Azure
Open the Azure portal.
Navigate to your web app
Search for and select App Services.
On the App Services page, select the name of your web app.
You have landed on the management page of your web app.
Check the pricing tier
In the left-hand navigation of your web app page, scroll to the Settings section and select Scale up (App Service plan).
Check to make sure that your web app is not in the F1 or D1 tier. Your web app's current tier is highlighted by a dark blue box.
Custom SSL is not supported in the F1 or D1 tier. If you need to scale up, follow the steps in the next section. Otherwise, close the Scale up page and skip the Scale up your App Service plan section.
Scale up your App Service plan
Select any of the non-free tiers (B1, B2, B3, or any tier in the Production category). For additional options, click See additional options.
Click Apply.
When you see the following notification, the scale operation is complete.
Create a free certificate (Preview)
The free App Service Managed Certificate is a turn-key solution for securing your custom DNS name in App Service. It's a fully functional TLS/SSL certificate that's managed by App Service and renewed automatically. The free certificate comes with the following limitations:
Note
The free certificate is issued by DigiCert. For some top-level domains, you must explicitly allow DigiCert as a certificate issuer by creating a CAA domain record with the value:
0 issue digicert.com .
To create a free App Service Managed Certificate:
In the Azure portal, from the left menu, select App Services > <app-name>.
From the left navigation of your app, select TLS/SSL settings > Private Key Certificates (.pfx) > Create App Service Managed Certificate.
Any non-naked domain that's properly mapped to your app with a CNAME record is listed in the dialog. Select the custom domain to create a free certificate for and select Create. You can create only one certificate for each supported custom domain.
When the operation completes, you see the certificate in the Private Key Certificates list.
Important
To secure a custom domain with this certificate, you still need to create a certificate binding. Follow the steps in Create binding.
Import an App Service Certificate
If you purchase an App Service Certificate from Azure, Azure manages the following tasks:
To purchase an App Service certificate, go to Start certificate order.
If you already have a working App Service certificate, you can:
Start certificate order
Start an App Service certificate order in the App Service Certificate create page.
Use the following table to help you configure the certificate. When finished, click Create.
Store in Azure Key Vault
Once the certificate purchase process is complete, there are few more steps you need to complete before you can start using this certificate.
Select the certificate in the App Service Certificates page, then click Certificate Configuration > Step 1: Store.
Key Vault is an Azure service that helps safeguard cryptographic keys and secrets used by cloud applications and services. It's the storage of choice for App Service certificates.
In the Key Vault Status page, click Key Vault Repository to create a new vault or choose an existing vault. If you choose to create a new vault, use the following table to help you configure the vault and click Create. Create the new Key Vault inside the same subscription and resource group as your App Service app.
Once you've selected the vault, close the Key Vault Repository page. The Step 1: Store option should show a green check mark for success. Keep the page open for the next step.
Verify domain ownership
From the same Certificate Configuration page you used in the last step, click Step 2: Verify.
Select App Service Verification. Since you already mapped the domain to your web app (see Prerequisites), it's already verified. Just click Verify to finish this step. Click the Refresh button until the message Certificate is Domain Verified appears.
Note
Four types of domain verification methods are supported:
Import certificate into App Service
In the Azure portal, from the left menu, select App Services > <app-name>.
From the left navigation of your app, select TLS/SSL settings > Private Key Certificates (.pfx) > Import App Service Certificate.
Select the certificate that you just purchased and select OK.
When the operation completes, you see the certificate in the Private Key Certificates list.
Important
To secure a custom domain with this certificate, you still need to create a certificate binding. Follow the steps in Create binding.
Import a certificate from Key Vault
If you use Azure Key Vault to manage your certificates, you can import a PKCS12 certificate from Key Vault into App Service as long as it satisfies the requirements.
In the Azure portal, from the left menu, select App Services > <app-name>.
From the left navigation of your app, select TLS/SSL settings > Private Key Certificates (.pfx) > Import Key Vault Certificate.
Use the following table to help you select the certificate.
When the operation completes, you see the certificate in the Private Key Certificates list. If the import fails with an error, the certificate doesn't meet the requirements for App Service.
Important
To secure a custom domain with this certificate, you still need to create a certificate binding. Follow the steps in Create binding.
Upload a private certificate
Once you obtain a certificate from your certificate provider, follow the steps in this section to make it ready for App Service.
Merge intermediate certificates
If your certificate authority gives you multiple certificates in the certificate chain, you need to merge the certificates in order.
To do this, open each certificate you received in a text editor.
Create a file for the merged certificate, called mergedcertificate.crt. In a text editor, copy the content of each certificate into this file. The order of your certificates should follow the order in the certificate chain, beginning with your certificate and ending with the root certificate. It looks like the following example:
Export certificate to PFX
Export your merged TLS/SSL certificate with the private key that your certificate request was generated with.
If you generated your certificate request using OpenSSL, then you have created a private key file. To export your certificate to PFX, run the following command. Replace the placeholders <private-key-file> and <merged-certificate-file> with the paths to your private key and your merged certificate file.
When prompted, define an export password. You'll use this password when uploading your TLS/SSL certificate to App Service later.
If you used IIS or Certreq.exe to generate your certificate request, install the certificate to your local machine, and then export the certificate to PFX.
Upload certificate to App Service
You're now ready upload the certificate to App Service.
In the Azure portal, from the left menu, select App Services > <app-name>.
From the left navigation of your app, select TLS/SSL settings > Private Key Certificates (.pfx) > Upload Certificate.
In PFX Certificate File, select your PFX file. In Certificate password, type the password that you created when you exported the PFX file. When finished, click Upload.
When the operation completes, you see the certificate in the Private Key Certificates list.
Openssl Generate Private Key
Important
To secure a custom domain with this certificate, you still need to create a certificate binding. Follow the steps in Create binding.
Upload a public certificate
Public certificates are supported in the .cer format.
In the Azure portal, from the left menu, select App Services > <app-name>.
From the left navigation of your app, click TLS/SSL settings > Public Certificates (.cer) > Upload Public Key Certificate.
In Name, type a name for the certificate. In CER Certificate file, select your CER file.
Click Upload.
Once the certificate is uploaded, copy the certificate thumbprint and see Make the certificate accessible.
Manage App Service certificates
This section shows you how to manage an App Service certificate you purchased in Import an App Service certificate.
Rekey certificate
If you think your certificate's private key is compromised, you can rekey your certificate. Select the certificate in the App Service Certificates page, then select Rekey and Sync from the left navigation.
Click Rekey to start the process. This process can take 1-10 minutes to complete.
Rekeying your certificate rolls the certificate with a new certificate issued from the certificate authority.
Once the rekey operation is complete, click Sync. The sync operation automatically updates the hostname bindings for the certificate in App Service without causing any downtime to your apps.
Note
If you don't click Sync, App Service automatically syncs your certificate within 48 hours.
Renew certificate
To turn on automatic renewal of your certificate at any time, select the certificate in the App Service Certificates page, then click Auto Renew Settings in the left navigation. By default, App Service Certificates have a one-year validity period.
Select On and click Save. Certificates can start automatically renewing 60 days before expiration if you have automatic renewal turned on.
To manually renew the certificate instead, click Manual Renew. You can request to manually renew your certificate 60 days before expiration.
Once the renew operation is complete, click Sync. The sync operation automatically updates the hostname bindings for the certificate in App Service without causing any downtime to your apps.
Note
If you don't click Sync, App Service automatically syncs your certificate within 48 hours.
Export certificateGenerate Private Key For Ssl Certificate Ubuntu
Because an App Service Certificate is a Key Vault secret, you can export a PFX copy of it and use it for other Azure services or outside of Azure.
To export the App Service Certificate as a PFX file, run the following commands in the Cloud Shell. You can also run it locally if you installed Azure CLI. Replace the placeholders with the names you used when you created the App Service certificate.
Generate Private Key From Ssl Certificate Template
The downloaded appservicecertificate.pfx file is a raw PKCS12 file that contains both the public and private certificates. In each prompt, use an empty string for the import password and the PEM pass phrase.
Delete certificate
Deletion of an App Service certificate is final and irreversible. Deletion of a App Service Certificate resource results in the certificate being revoked. Any binding in App Service with this certificate becomes invalid. To prevent accidental deletion, Azure puts a lock on the certificate. To delete an App Service certificate, you must first remove the delete lock on the certificate.
Select the certificate in the App Service Certificates page, then select Locks in the left navigation.
Find the lock on your certificate with the lock type Delete. To the right of it, select Delete.
Now you can delete the App Service certificate. From the left navigation, select Overview > Delete. In the confirmation dialog, type the certificate name and select OK.
Automate with scriptsGenerate Private Key FileAzure CLIPowerShellHow To Generate Private Key From Ssl CertificateMore resourcesComments are closed.
|
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |