Export App Service Certificate and set up a password

[Guest Joe_Chen]

This blog will guide how to export the App Service Certificate from Azure Portal and set up a password for the certificate in Windows and export it with password by using PowerShell.

 

 

 

When we create App Service Certificate (Add and manage TLS/SSL certificates - Azure App Service | Microsoft Learn) in Azure Portal, sometime we are not using it in the App Service but use it for Azure VM or on-prem VM. Moreover, we will use it in some Azure resources (such as upload the certificate to Azure Application Gateway).

 

 

 

However, after you export the App Service Certificate from Azure Portal, when you are going to upload it to Azure Application Gateway or use it in the Azure VM or on-prem VM, you would find out sometimes it would need the "password". But you don't know what the password is for the certificate. This is because when we export App Service Certificate, it is without password by default so we need to set it up manually by ourselves.

 

 

 

In this article, we will show you how to export the App Service Certificate and set up the password for certificate in Windows:

 

Export the App Service Certificate in Azure Portal and set up the password in Windows

 

1. Go to your App Service Certificate and click "Export Certificate" -> "Open Key Vault Secret"
   

 

 

1. Click the current version of certificate
   

 

 

1. Click "Download as a certificate"
   

 

 

1. Right click on the download .pfx certificate and click "Install PFX"
   

 

 

1. Select "Current User"
   

 

 

1. Make sure that select the correct .pfx file
   

 

 

1. Keep the password empty and check the "Mark this key as exportable. This will allow you to backup or transport your keys at a latter time" checkbox
   

 

 

1. Select "Place all certificates in the following store" and Choose "Personal" for Certicate store
   

 

 

1. Click "Finish"
   
2. Open Certificate Manager by searching "certmgr.msc" in Windows
   

 

 

1. Select "Certificates - Current User" -> "Personal" -> "Certificate". Then right click on the target certificate and select "All Tasks" -> "Exports…"
   

 

 

1. Choose "Yes, export the private key"
   

 

 

1. Choose "Personal Information Exchange - PKCS #12 (.PFX)" and make sure check the "Include all certificates in the certification path if possible" and "Enable certificate privacy"
   

 

 

1. Select the "Password" and enter the password
   

 

 

1. Give a filename to save this certificate
   

 

 

1. Click "Finish"
   

 

Export the App Service Certificate with the password by PowerShell

 

You could also use the PowerShell simply to export it by following script:

 

 

 

#Connect to Azure and select subscription

Login-AzureRmAccount

Select-AzureRMSubscription -SubscriptionName "<name of subscription containing keyvault>"

 

#Obtain the secret from keyvault

$vaultName = '<name of Keyvault>'

$secretName = '<name of secret containing certificate>'

$certString = Get-AzureKeyVaultSecret -VaultName $vaultName -Name $secretName

 

#Create a PFX from the secret and write to disk

$kvSecretBytes = [system.Convert]::FromBase64String($certString.SecretValueText)

$certCollection = New-Object System.Security.Cryptography.X509Certificates.X509Certificate2Collection

$certCollection.Import($kvSecretBytes,$null,[system.Security.Cryptography.X509Certificates.X509KeyStorageFlags]::Exportable)

$password = '<required password for PFX>'

$protectedCertificateBytes = $certCollection.Export([system.Security.Cryptography.X509Certificates.X509ContentType]::Pkcs12, $password)

$pfxPath = "C:\temp\$secretName.pfx"

[system.IO.File]::WriteAllBytes($pfxPath, $protectedCertificateBytes)

 

 

 

 

 

 

Congratulation, after these steps, now you will get a certificate with password! At last, would like add a kind reminder below:

 

 

Hope this article is helpful for you, thank you for reading :)

 

 

 

Reference:

 

Azure: Exporting App Service Certificates - TechNet Articles - United States (English) - TechNet Wiki (microsoft.com)

 

Continue reading...