Automated process for a web site to receive a secure socket layer certificate

• US 8,086,848 B2
• Filed: 03/09/2010
• Issued: 12/27/2011
• Est. Priority Date: 06/25/2004
• Status: Active Grant

• Current Assignee: Go Daddy Operating Company LLC (GoDaddy, Inc.)
• Original Assignee: Go Daddy Group Incorporated (GoDaddy, Inc.)
• Inventors: Thayer, Wayne, Reilly, Kevin, Jilg, Justin
• Primary Examiner(s): LAFORGIA, CHRISTIAN A
• Application Number:
  US12/719,992
• Publication Number:
  US 20100161971A1
• Time in Patent Office: 658 Days
• Field of Search: 713/152, 713156-157
• US Class Current: 713/156
• CPC Class Codes: H04L 63/0823 using certificates cryptographic mechanisms or cryptographic arrangements for entity authentication involving certificates H04L9/3263
• CPC Class Codes: H04L 63/166 at the transport layer
• CPC Class Codes: H04L 67/02 based on web technology, e.g. hypertext transfer protocol [HTTP]

Abstract

The present invention provides systems and methods for enabling encrypted communication capabilities for a Subscriber'"'"'s Web Site, thereby allowing Customers to access the Subscriber'"'"'s Web Site in a secure manner. A Hosting Provider, that hosts the Subscriber'"'"'s Web Site, and a Certificate Authority (CA), that verifies the identity of the Subscriber, provide the Subscriber'"'"'s Web Site with Secure Sockets Layer (SSL) encrypted communications capability. The Hosting Provider and CA communicate directly with each other as needed, typically via the Internet, without using the Subscriber as an intermediary in their communications.

Claims

1. A method, comprising the steps of:

a) receiving, by a Certificate Authority, a request for a Secure Sockets Layer Certificate for a Web Site hosted by a Hosting Provider, said request being received from an owner of said Web Site, said Hosting Provider comprising an entity that is different than said owner of said Web Site;

b) receiving, by said Certificate Authority, a Certificate Signing Request directly from said Hosting Provider, said Certificate Signing Request comprising a public key and a distinguished name for said Web Site, said public key comprising part of a key pair generated by said Hosting Provider according to Public-Key Infrastructure protocol;

c) verifying, by said Certificate Authority, the identity of said owner of said Web Site;

d) upon successful verification of the identity of said owner of said Web Site, creating and signing, by said Certificate Authority, said Secure Sockets Layer Certificate; and

e) transmitting, by said Certificate Authority, said Secure Sockets Layer Certificate directly to said Hosting Provider for installation on said Web Site, wherein Steps b) though e) are accomplished without said owner of said Web Site being contacted by said Certificate Authority or said Hosting Provider.

2. The method of claim 1, wherein said Hosting Provider and said Certificate Authority are operated by a common Facilitator'"'"'s Web Server.

3. The method of claim 1, wherein said Hosting Provider and said Certificate Authority are operated on separate servers.

4. The method of claim 1, wherein said Certificate Authority verifies the identity of said owner of said Web Site by comparing responses from said owner with information available from information services available over the Internet.

5. The method of claim 1, wherein said Certificate Authority is a root Certificate Authority.

6. The method of claim 1, wherein said Certificate Authority is linked to a root Certificate Authority.

7. A method, comprising the steps of:

a) receiving, by a Hosting Provider that provides a plurality of hardware and software necessary to place a Web Site on the Internet, a request for a Secure Sockets Layer Certificate for said Web Site, said request being received from an owner of said Web Site, said Hosting Provider comprising an entity that is different from said owner of said Web Site;

b) generating, by said Hosting Provider, a key pair comprising a public key and a private key according to Public-Key Infrastructure protocol;

c) generating, by said Hosting Provider, a Certificate Signing Request comprising said public key and a distinguished name for said Web Site;

d) transmitting, by said Hosting Provider, said Certificate Signing Request directly to a Certificate Authority;

e) receiving, by said Hosting Provider, said Secure Sockets Layer Certificate directly from said Certificate Authority; and

f) installing, by said Hosting Provider, said Secure Sockets Layer Certificate on said Web Site, wherein Steps b) though f) are accomplished without said owner of said Web Site being contacted by said Certificate Authority or said Hosting Provider.

8. The method of claim 7, wherein said Hosting Provider and said Certificate Authority are operated by a common Facilitator'"'"'s Web Server.

9. The method of claim 7, wherein said Hosting Provider and said Certificate Authority are operated on separate servers.

10. The method of claim 7, wherein said Certificate Authority verifies the identity of said owner of said Web Site by comparing responses from said owner with information available from information services available over the Internet.

11. The method of claim 7, wherein said Certificate Authority is a root Certificate Authority.

12. The method of claim 7, wherein said Certificate Authority is linked to a root Certificate Authority.

13. A method, comprising the steps of:

a) receiving, by a Hosting Provider hosting a Web Site, a request for a Certificate Signing Request directly from a Certificate Authority, said Hosting Provider comprising an entity that is different than an owner of said Web Site;

b) generating, by said Hosting Provider, a key pair comprising a public key and a private key according to Public-Key Infrastructure protocol;

c) generating, by said Hosting Provider, a Certificate Signing Request comprising said public key and a distinguished name for said Web Site;

d) transmitting, by said Hosting Provider, said Certificate Signing Request directly to a Certificate Authority;

e) receiving, by said Hosting Provider, said Secure Sockets Layer Certificate directly from said Certificate Authority; and

f) installing, by said Hosting Provider, said Secure Sockets Layer Certificate on said Web Site, wherein Steps b) though e) are accomplished without said owner of said Web Site being contacted by said Certificate Authority or said Hosting Provider.

14. The method of claim 13, wherein said request for said Certificate Signing Request was transmitted by said Certificate Authority subsequent to receiving, from said owner of said Web Site, a request for a Secure Sockets Layer Certificate for said Web Site.

15. The method of claim 13, wherein said Hosting Provider and said Certificate Authority are operated by a common Facilitator'"'"'s Web Server.

16. The method of claim 13, wherein said Hosting Provider and said Certificate Authority are operated on separate servers.

17. The method of claim 13, wherein said Certificate Authority verifies the identity of said owner of said Web Site by comparing responses from said owner with information available from information services available over the Internet.

18. The method of claim 13, wherein said Certificate Authority is a root Certificate Authority.

19. The method of claim 13, wherein said Certificate Authority is linked to a root Certificate Authority.