I'm building a service in Azure. Rigth now I have 2 servers
Worker-1 does http, ftp and a couple of .exe services that are running around the clock. Both DC and Worker are part of a .com domain I've set up.
I needed to secure some HTTPS service on Worker-1 so I've got a "domain verified" SSL certificate. I now need to secure that FTP service that is running too...
1) Can I use the same certificate or do I have to get another "domain verified" for the ftp.foo.com (ftp)?
2) Getting a wildcard SSL certificate solves the problem above, where I can secure both (and more) ftps://asd1.foo.com and https://foo.com?
Please look at 1) as two simple certificates are cheaper than a wildcard so for now it might be the best economical solution.
3) What if I moved the FTPS service to another server? If I create Worker-2 and set up FTPS service on that. Can I still utilize the same certificate? Guessing I at least need a wildcard here as I still have the https running on Worker-1.
Or do I in this case need a "Organization Verified" certificate? I understand there are three types, DV, OV and EV certificates. Could I in 3) simply add the certificates to the Active Directory and everything magically runs? :) Wishful thinking, I'm not sure how certificates work a cross servers in a domain.