ソースを表示

SSL certificates are normally utilized with ecommerce shopping carts, or anywhere you want to collect details from a user securely on your web site. If you use a secure server certificate with a form and that form emails the results to you keep in thoughts that the email is not secure.

SSL (Secure Sockets Layer): Creates an encrypted link among a net server and a browser. CA (Certificate Authority): The vendor you will get the secure server certificate from...

What is SSL?

SSL certificates are usually used with ecommerce shopping carts, or anywhere you want to collect information from a user securely on your web site. If you use a secure server certificate with a form and that form emails the outcomes to you maintain in mind that the e-mail is not secure.

SSL (Secure Sockets Layer): Creates an encrypted link among a net server and a browser. CA (Certificate Authority): The vendor you will get the secure server certificate from CSR (Certificate Signing Request): A text file generated by a web server. A CSR looks like this:

-----Begin NEW CERTIFICATE REQUEST-----

MIIDGgBNAGkAYwByAG8AcwBvAGYAdAAgAFIAUwBBACAAUwB

AG4AZQBsACAAQwByAHkAcAB0AG8AZwByAGEAcABoAGkAYwl

L0ygNwwNIvKLMPq4/LcUkZ9Oo4AssXW5mvvhHWGz2RWYRhrw8o

-----End NEW CERTIFICATE REQUEST-----

Very first, you require to determine whether or not to use your hosting shared SSL certificate if they provide it. The URL to your retailer will appear a thing like:

https://theirserver.com/youruserid/your/path/to/store.html

Or do you want to get your own SSL certificate? The URL will appear like:

https://yourdomainname.com

If you make a decision to use your hosts' shared secure server certificate, then all you need to have to do is uncover out the path you need to use to call your files securely, and you will be on your way.

If you determine to get your own SSL certificate, this is generally what takes place.

You first need to choose who you are going to get your SSL certificate from. It is a very good idea to make sure your host supports your certain vendor. Some certificate authority vendors are:

* Thawte

* Verisign

* Comodo

* You can also critique several vendors at a glance at WhichSSL

Ahead of getting your own SSL certificate, you will need to do some reading on what your chosen Certificate Authority needs for a secure certificate, and you will also need to have to come up with some documentation. There are numerous steps to acquiring a secure server certificate, as soon as you have decided on a vendor.

This is an overview, not written in stone. Every single CA is distinct, so make confident you read their documentation and what they demand. Here is an thought of what they want:

All documentation that is requested ought to match *precisely*. Secure certificate authorities will verify that your organization actually exists, so they know they are issuing to the correct business. You will want to prove that the Organization Name and the Domain name are in fact yours to use.

Actions you will be taking:

* Gather needed documentation

* Have your host create a CSR

* Complete certificate authority on the web application

* Certificate authority will process your request

* Pickup and install your SSL certificate (normally an URL is emailed to you to download the secure server certificate)

* Based on the vendor, it can take a few hours to a few days.

* Send secure certificate to host for installation. (Send in plain text)

When your net hosting provider receives this information they will create the CSR and send it back to you in plain text. You then send it on to Verisign or Thawte, or whoever you have chosen as your secure certificate authority. They will then produce a SSL certificate for you which you will send back to your host for installation. Your net host may charge a fee for installation in addition to what your SSL certificate vendor charges.

Some thing to believe about:

If you have decided to obtain your own SSL certificate, you will need to have to choose how you want your URL to be named. If you, as a rule, call your domain name in your coding as www.yourdomainname.com, then make sure you indicate this to your host when you request a CSR from them. If you don't, and you get the certificate for yourdomainname.com (without having the www), this will lead to browser errors, creating the certificate appear insecure, and you will need to adjust your coding.

Usually use your self or your company as technical contact.

How to tell if a site is secure?

Following you've browsed to a web site securely employing https:// in the URL, appear on the lower correct hand side of your browser. You really should see a closed lock. This will tell you the web site is secure. [http://www.entrust.comwww.entrust.com/token-security.htm token security] [http://www.entrust.comwww.entrust.com/enterprise-authentication/two-factor.htm two factor authentication] [http://www.entrust.comwww.entrust.com/pki/admin_services/ entrust esp]