I could not find a link that describes Domain certificate, I am familiar with SSL certificates, and certificate authority but I don't know about Domain certificate.
and what is Multi-Domain certificate.
thanks
From the description in some CAs (e.g. Comodo), a multi-domain certificate seems to be a certificate that can be used with multiple host names: this is done by putting multiple subject alternative name entries in the certificate. This is useful if your server has multiple hosts on the same IP address (but does not support server name indication (SNI) which is not widespread yet). In this case, only one certificate may be used for all the hosts sharing the same IP address (before HTTP has a chance to say to which particular host it wants to talk to), so this certificate has to be valid for all the hosts on that server (with same IP address and port).
That's not the same as a wildcard certificate, which contains a single name, but with a wildcard to represent a pattern in the name.
"Domain certificate" certainly depends on the context, but it could either be a "single domain" certificate (as opposed to a multi-domain certificate), or, in the context of Microsoft IIS:
[...] an internal certificate that does not
have to be issued by an external
certification authority (CA).
I Open IIS7 and tried to create a domain certificate, it seems just a certificate issued from CA.
Related
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.
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've read a bit about SSL certificates, and in particular I've read that an SSL certificate "requires a dedicated IP address". Now, I'm unsure of the meaning of this; does it mean that the certificate requires a dedicated IP address separate from the IP address used for normal HTTP communication, or just that it can't share the IP address with other SSL certificates?
To clarify, I have a VPS with a dedicated IP address. The VPS is hosting quite a few different sites, including several subdomains of the main site, but only the main site and the subdomains requires SSL. Can I simply purchase an SSL certificate for *.example.com using my current IP address, or do I need to get one that is separate from the other sites on the VPS? Or even worse, do I need to get one that is separate from all HTTP traffic on the server? Keep in mind that none of the other sites needs SSL.
Thanks for any clarification on the topic.
Edit: Some sources for my worries:
http://symbiosis.bytemark.co.uk/docs/symbiosis.html#ch-ssl-hosting
Is it necessary to have dedicated IP Address to install SSL certificate?
There's no such thing as "SSL certificate". The term is misleading. X.509 certificates can be issued for different purposes (as defined by their Key Usage and Extended Key Usage "properties"), in particular for securing SSL/TLS sessions.
Certificates don't require anything in regards to sockets, addresses and ports as certificates are pure data.
When securing some connection with TLS, you usually use the certificate to authenticate the server (and sometimes the client). There's one server per IP/Port, so usually there's no problem for the server to choose what certificate to use.
HTTPS is the exception — several different domain names can refer to one IP and the client (usually a browser) connects to the same server for different domain names. The domain name is passed to the server in the request, which goes after TLS handshake.
Here's where the problem arises - the web server doesn't know which certificate to present. To address this a new extension has been added to TLS, named SNI (Server Name Indication). However, not all clients support it. So in general it's a good idea to have a dedicated server per IP/Port per domain. In other words, each domain, to which the client can connect using HTTPS, should have its own IP address (or different port, but that's not usual).
SSL certificates do not require a dedicated IP address. SSL certificates store a so called common name. Browser interpret this common name as the DNS name of the server they are talking to. If the common name does not match DNS name of the server that the browser is talking to, the browser will issue a warning.
You can get a so called wildcard certificate, that would be admissible for all hosts within a certain domain.
...following up on #Eugene's answer with more info about the compatibility issue...
According to this page from namecheap.com SNI does not work on:
Windows XP + any version Internet Explorer (6,7,8,9)
Internet Explorer 6 or earlier
Safari on Windows XP
BlackBerry Browser
Windows Mobile up to 6.5
Nokia Browser for Symbian at least on Series60
Opera Mobile for Symbian at least on Series60
Web site will still be available via HTTPS, but a certificate mismatch error will appear.
Thus, as we enter 2016 I would venture to stick my neck out there and say, "If you're building a modern website anyway (not supporting old browsers), and if the project is so small that it cannot afford a dedicated IP address, you'll probably be fine relying on SNI." Of course, there are thousands of experts who would disagree with this, but we're talking about being practical, not perfect.
The ssl certificate commmon name has to match the domain name. You don't have any requisite over the ip address, unless it's a limitation imposed by the certificate provider or the http server software.
Edit: looking into the web, it seems that the rumor has been spread because Apache's ssl plugin doesn't have (at least it didn't have in 2002) any mechanism to use different certificate based on the hostname. In such scenario you would have to run two different Apache web servers on the two different IP addresses.
Anyway in your configuration you shouldn't have any problem using only one IP because you don't have to use two different certificates (because you plan to use a wildcard certificate).
I would try anyway configuring the webserver with a self signed certificate before spending money for a second ip or certificate.
Edit 2: reference apache documentation:
http://httpd.apache.org/docs/2.2/vhosts/name-based.html
It seems like now (apache >= 2.2.12) it is supported
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.