We have used wild card subdomain to our web app running iis.it is working fine.Now we purchases ssl and implemented , it is working for https://www.xyz.domain.com or https://www.domain.com but did not work on https://domain.com.
Please help|||||
I assume your SSL certificate was issued for www.domain.com. Typically, when you purchase an SSL certificate that is "wild card", the CA puts two DNS names in the subject alternative name of the certificate. For you, it is probably www.domain.com and *.www.domain.com. It is unlikely that the certificate is issued for domain.com because it would not be valid for www.xyz.domain.com since wildcards only go one sub domain deep.
You need to work with your CA on getting the right kind of certificate. You need a certificate that is valid for domain.com, www.domain.com, and *.www.domain.com. There is nothing you can do to work around this other than get a new certificate with the correct SAN.
Related
My company has a SSL certificate for *.mycompany.com. We use this certificate for many critical services.
Marketing team owns www.mycompany.com website (WordPress) and wants a SSL certificate for it.
Can we issue a specific certificate for www.mycompany.com?
Yes. as far as the certificate is concerned there is no relationship between different servers. You could have five different servers with five different certificates and as long as each one of them is valid there wouldn't be a problem. (it might cause a problem if the certificate changes mid-session)
You should however be aware that www.example.com would also be usable as a certificate for any of your other 'critical' services that operate on www.example.com, you could have a security issue there.
I develop a website with Symfony2 and I put it in HTTPS.
I have several questions:
The only way to don't have an error message on my browser when I go to my website is to have an SSL certificate?
How the installation of the SSL certificate on a website works?
Verisign offers SSL certificates from 450€/year ( http://www.symantec.com/fr/fr/page.jsp?id=compare-ssl-certificates ). It's quite expensive. Is there other good solutions to have a cheaper certificate?
If your site is not shop or something commercial, you can get free cert at startssl.com
See awesome tutorail
(Installing certificate in nginx is almost the same with apache)
UPD
Now use letsencrypt :)
Certificates tell the client you can be trusted. Web browsers come loaded with trusted keys from third parties. Your browser checks the key of the cert coming in and if it is in the list it allows SSL connection (if the IP address in the cert etc is correct). This is why it costs as no doubt the cert providers have their own expenses to be added to browsers and to turn a profit etc.
You can of course produce you own certificate but they won't be recognised by your clients machine. The user then has to explicitly accept the cert - some browsers like chrome make this hard as it is a security risk.
Google should help you find the best cert deals from trusted providers.
Your hosting provider should be able to help you set up your cert. If your self hosting that should be its own question as it could have different answers depending on your set up.
I want to use same SSL certificate in multiple servers, which type of SSL certificate should I use? Unified SSL certificate? or Wildcard SSL certificate?
Thanks
Any certificate can be installed on multiple servers but your question requires more information on how you want to be advised.
A wildcard SSL certificate will secure any subdomain that the Wildcard character is on. So if you have a certificate for *.domain.com then you can secure
secure.domain.com
bob.domain.com
charlie.domain.com
and the list can go on, however it won't work for sub.secure.domain.com as the wildcard only does the single level.
A unified certificate, depending on the provider would only give you 3 subdomains.
mail, owa and autodiscover.domain.com
Also a standard certificate you can generally add SAN's too which will allow you to add subdomains under extra costs, but if you are only looking to secure 2 subdomains then a certificate with 1 SAN would be cheaper in most cases than a wildcard.
Give us an example of what you are trying to do and people can probably advise you better.
Securing Multiple Servers With One SSL Certificate
To move your certificate between servers you will need to install the certificate on the same web server that you generated the CSR from. You can then export the SSL certificate and its private key to a PKCS#12 file, or if it is an non-Windows based server you will be able to copy the key and certificate files.
Click HERE for more details:
Wildcard SSL Certificates allow you to secure multiple sub domains on the same domain name, thereby saving you time and money, and of course you do not need to manage multiple SSL Certificates on the same server.
I configured SSL on IIS 7 for my ASP.NET website. But its giving error that Server certificate does not match the URL, even after providing the same name "localhost" in certificate friendly name as that of my server.
I also changed the name of the server as ASP-DELL i.e. the name of my computer and created a certificate with that name and started the website as http://ASP-DELL/HC/index.aspx but it still showing this in Google Chrome:
Please help!
What's missing (or at least unclear) in your question is what the common name (not friendly name) of the certificate you installed/purchased/configured....
Certificates are issued to a specific common name/host name, and the url must match it specifically.
Until SANs (subject alternative name) became common, I recall the days when one had to purchase 2 certificates for the "www" web site and the "site without the www". These days there are also "wildcard certificates".
Its also unclear what type of certificate you are referring to, self-signed/test or is it something you purchased? I wouldn't think a certificate provider will let you purchase a certificate with a common name of "localhost" (but then again I could be wrong).
In production, certificate common name will equate to your DNS fully qualified url -e.g:
DNS: www.google.com
Certificate common name: www.google.com
if the certificate includes a SAN, then default would likely be: google.com
this means the certiifcate will work with or without "www" (otherwise it would only work specifically for www.google.com)
I think by adding domain of your network with your computer name could help to fix it as I remember I went through similar situation.
can you change it from
http://ASP-DELL/HC/index.aspx
To
http://ASP-DELL.YourNetworkDomain/HC/index.aspx
I'm pretty new to the https world, so bear with me.
There are 2 web-servers involved:
Webserver1 has been in the organization a few years and is hosting/running multiple websites with https encryption (app1.ourcompany.com, app2.ourcompany.com, etc). It has a valid, signed certificate.
Webserver2 is a new server, for which I am responsible. I am tasked with setting up https and getting the certificate, etc. It has a web app running on it, but it does not have a domain name (only has an IP address)...which as I recently learned, is a requirement for a signed certificate.
What I'd like to know is this -- is it possible to set up a site on Webserver1 that points to the site I'm hosting on Webserver2 (ie SiteOnWebserver2.ourcompany.com) which also utilizes the Webserver1's signed/verified certificate?
Thanks for your time, SO gurus!
--Dan
A regular SSL certificate is valid for only a single domain name (such as app1.ourcompany.com). If this is the type of certificate currently being used then the existing SSL certificates will not work on your new server. If you did try this you would get an error in the browser saying that the site's domain name doesn't match the name in the SSL certificate.
The other option is to use a wildcard SSL certificate. These kinds of certificates are assigned to a certain parent domain (like ourcompany.com) and will work for all subdomains. This kind of certificate would work for app1.ourcompany.com, app2.ourcompany.com, as well as your SiteOnWebserver2.ourcompany.com.