Domain SSL certificate Replacement
Hello Experts
We currently have a UCC SSL certificate purchased from GODADDY,
And we want to change the SSL certificate to a WILDCARD.
My questions are as follows:
1. What is the Best practice for demolish the current cert and creating the new wildcard one.
2. What to do with the Implications on the Exchange, ActiveSync sync while without an SSL.
3. How to Verify that the new * SSL will be able to work with multiple private keys, which means different servers. Please check also if there's a private-keys/servers limitation.
I would be glad if you can assist me on this issue,
Thank you.
We currently have a UCC SSL certificate purchased from GODADDY,
And we want to change the SSL certificate to a WILDCARD.
My questions are as follows:
1. What is the Best practice for demolish the current cert and creating the new wildcard one.
2. What to do with the Implications on the Exchange, ActiveSync sync while without an SSL.
3. How to Verify that the new * SSL will be able to work with multiple private keys, which means different servers. Please check also if there's a private-keys/servers limitation.
I would be glad if you can assist me on this issue,
Thank you.
Last Comment
ASKER CERTIFIED SOLUTION
THIS SOLUTION IS ONLY AVAILABLE TO MEMBERS.
View this solution by signing up for a free trial.
Members can start a 7-Day free trial and enjoy unlimited access to the platform.
Web Servers
A web server refers to the software that helps to deliver web content that can be accessed either through the Internet or through an intranet. The primary function of a web server is to store, process and deliver web pages to clients. The communication between client and server takes place using the Hypertext Transfer Protocol (HTTP). The most common use of web servers is to host websites, but there are other uses such as gaming, data storage, running enterprise applications, handling email, FTP, etc.
33K
Questions
--
Followers
--
Top Experts
Get a personalized solution from industry experts
TRUSTED BY
How woud you know that this will work. You must knowthat wildcard certificate have only ONE PRIVATE KEY it just have more dns names in side of it. So if you wanted this working you must have for every wilde name A grade DNS to your server and import certificate inside every IIS instance.
You can also do one thing if you have more domains you can buy Certificate for your own microsoft Certification Autority and you can then make any certificate and all of them will be trusted becouse ROOT CA signs your CA and then you are save.
reed more here http://www.davidpashley.com/articles/cert-authority.html
Best practice is to make new Certificate on autority then use replace function on every servis for example in IIS it is import new certificate and then activate of it. After you replace certificate on every service you will go to managment panel of CA and revoke your certiciate (rewoking is dont trust this cert any more) and ict the same like destruction becouse it cant be used anywere.