Migrating existing SSL certificate
Recently I had a requirement to close my on one of the Azure subscription and migrate my web apps and associated SSL certificate for the custom domain (also called ssl binding - required to enable Https endpoint for the webapp hosted on azure) which I had purchased to the new azure subscription.
This blog will highlight some of the important steps I followed in order to achieve this as below:-
Recently I had a requirement to close my on one of the Azure subscription and migrate my web apps and associated SSL certificate for the custom domain (also called ssl binding - required to enable Https endpoint for the webapp hosted on azure) which I had purchased to the new azure subscription.
This blog will highlight some of the important steps I followed in order to achieve this as below:-
Go to your certificate (you want to migrate) in Azure subscription Key vault and go down to Export certificate settings.
- Under Download certificate from Key Vault section, click Key vault secret and download the Current version of the certificate by clicking "Download as a certificate" button on your local filesystem. This will download the certificate in .pfx (Public Key Exchange) file format.
- Now right click on the downloaded pfx file and click Install PFX (certificate) option from the context menu . This will open the Import/Export Certificate Wizard.
- Run this Import /Export certificate wizard to first import the certificate from the pfx file and install it to the local certificate store on your local system and then Export it completely in the pfx file format and save it on the local file system. I found the detailed steps for this here - https://dotnetdevlife.wordpress.com/2019/06/06/export-azure-app-service-certificate-upload-to-azure-app-service-website/
- Now you can upload the exported file (pfx) from the file system to new azure subscription (ssl binding ) or new server wherever you want to migrate to or attach to your web application.
Some Fundamental Points to Note-
The .pfx contains the complete info about certificate i.e Private as well a Public key of the certificate and other encrypted information and should never be communicated or shared outside but is required to import/export a certificate. On the other hand the .cer file only contains the public key and some server information and is generally communicated/exchanged between servers but is not used to export/import a certificate. Basically when we access any HTTPS site on a server , the public key is used to communicate and encrypt messages between client and server and private key is used only to verify and authenticate at the server end. So basically private key is never transmitted. This is the way most security protocols work ...
Hope this was helpful!
Hope this was helpful!
Very informative article covering fundamental points
ReplyDeleteIt is truly a well-researched content and excellent wording. I got so engaged in this material that I couldn’t wait to read. I am impressed with your work and skill. Thanks.moover click key
ReplyDeleteIts very Great to see this post....Quite Informative...
ReplyDeleteVery Useful and knowledgeable....
ReplyDeleteThanks
Regards
Rahul
https://transformingworld-developer-edition.ap7.force.com/
Best Casino Hotels and Resorts in Las Vegas, NV
ReplyDeleteFind the 안산 출장샵 best hotel and casino hotels and resorts in Las Vegas, NV. We compare the cheapest 전주 출장마사지 and quickest 여주 출장안마 ways to get from Casino Hotels 제주 출장안마 & 경주 출장마사지 Resorts to