IP Library Granted Patent US 9,258,128
Granted Patent B1
US 9,258,128 · App. 14/016,017 · Granted Feb 9, 2016

Systems and methods for creating customer-specific tools for generating certificate signing requests

View Patent ↗
Loading inventors, assignments & file history…
Monitor This Case
Get email alerts when status or documents change.
Order Certified Copies
Most orders are placed with the USPTO same day — all within 24 business hours.
Order via The Patent Place →
Pre-filled with this patent's details
Quick Facts
Patent No.
US 9,258,128
App. No.
14/016,017
Granted
Feb 9, 2016
Kind
B1
Abstract

A method for creating customer-specific tools for generating certificate signing requests may include (1) identifying a request from a customer for a tool for generating a certificate signing request for a digital certificate, (2) creating, in response to the request, a customer-specific version of the tool that is unique to the customer by injecting information into the customer-specific version of the tool that (a) uniquely identifies the customer and (b) identifies a desired encryption algorithm for the digital certificate and/or a desired certificate authority for the digital certificate, (3) configuring the customer-specific version of the tool to generate the certificate signing request using the injected information, and (4) providing the customer-specific version of the tool to the customer to enable the customer to generate, using the customer-specific version of the tool, the certificate signing request without having to manually provide the injected information.

Claims (81)

1. A computer-implemented method for creating customer-specific tools for generating certificate signing requests, at least a portion of the method being performed by a computing device comprising at least one processor, the method comprising:

identifying a request from a customer for a tool for generating a certificate signing request for a digital certificate;

creating, in response to the request, a customer-specific version of the tool that is unique to the customer by injecting information that is necessary to generate the certificate signing request into an executable file of the customer-specific version of the tool, wherein the information:

uniquely identifies the customer; and

identifies at least one of a desired encryption algorithm for the digital certificate and a desired certificate authority for the digital certificate;

configuring the customer-specific version of the tool to generate the certificate signing request using the injected information; and

providing, to the customer, the customer-specific version of the tool that already contains the injected information necessary to generate the certificate signing request to enable the customer to generate, using the customer-specific version of the tool, the certificate signing request without having to manually provide the injected information.

2. The method of claim 1 , wherein identifying the request from the customer for the tool comprises at least one of:

receiving a request from the customer to purchase the digital certificate; and

receiving a request from the customer to download the tool.

3. The method of claim 1 , wherein the customer-specific version of the tool is configured to automatically open and extract the injected information upon execution.

4. The method of claim 1 , further comprising, prior to creating the customer-specific version of the tool, identifying the information that uniquely identifies the customer by at least one of:

retrieving at least a portion of the information that uniquely identifies the customer from a customer database; and

requesting and receiving, from the customer, the information that uniquely identifies the customer in response to receiving at least one of:

a request from the customer to purchase the digital certificate; and

a request from the customer to download the tool.

5. The method of claim 1 , further comprising, prior to creating the customer-specific version of the tool, identifying the desired encryption algorithm for the digital certificate by at least one of:

ascertaining the desired encryption algorithm for the digital certificate from the customer's purchase history; and

requesting and receiving, from the customer, an identification of the desired encryption algorithm for the digital certificate in response to receiving at least one of:

a request from the customer to purchase the digital certificate; and

a request from the customer to download the tool.

6. The method of claim 1 , further comprising, prior to creating the customer-specific version of the tool, identifying the desired certificate authority for the digital certificate by at least one of:

ascertaining the desired certificate authority from a web portal chosen by the customer when submitting the request for the tool; and

ascertaining the desired certificate authority from a version of the tool requested by the customer.

7. The method of claim 1 , further comprising, upon creation of the digital certificate:

identifying an additional request from the customer for an additional tool for installing the digital certificate;

creating, in response to the additional request, a customer-specific version of the additional tool that is unique to the customer and that includes the digital certificate;

configuring the customer-specific version of the additional tool to install the digital certificate using the included digital certificate; and

providing the customer-specific version of the additional tool to the customer to enable the customer to install, using the customer-specific version of the additional tool, the digital certificate without having to manually locate the digital certificate.

8. The method of claim 7 , wherein the tool for generating the certificate signing request and the additional tool for installing the digital certificate comprise the same tool.

9. A system for creating customer-specific tools for generating certificate signing requests, the system comprising:

an identification module that identifies a request from a customer for a tool for generating a certificate signing request for a digital certificate;

a tool creation module that creates, in response to the request, a customer-specific version of the tool that is unique to the customer by injecting information that is necessary to generate the certificate signing request into an executable file of the customer-specific version of the tool, wherein the information:

uniquely identifies the customer; and

identifies at least one of a desired encryption algorithm for the digital certificate and a desired certificate authority for the digital certificate;

a tool configuration module that configures the customer-specific version of the tool to generate the certificate signing request using the injected information; and

a communication module that provides, to the customer, the customer-specific version of the tool that already contains the injected information necessary to generate the certificate signing request to enable the customer to generate, using the customer-specific version of the tool, the certificate signing request without having to manually provide the injected information; and

at least one processor configured to execute the identification module, the tool creation module, the tool configuration module, and the communication module.

10. The system of claim 9 , wherein the identification module identifies the request from the customer for the tool by at least one of:

receiving a request from the customer to purchase the digital certificate; and

receiving a request from the customer to download the tool.

11. The system of claim 9 , wherein the tool configuration module configures the customer-specific version of the tool to automatically open and extract the injected information upon execution.

12. The system of claim 9 , wherein, prior to creation of the customer-specific version of the tool, the identification module identifies the information that uniquely identifies the customer by at least one of:

retrieving at least a portion of the information that uniquely identifies the customer from a customer database; and

requesting and receiving, from the customer, the information that uniquely identifies the customer in response to receiving at least one of:

a request from the customer to purchase the digital certificate; and

a request from the customer to download the tool.

13. The system of claim 9 , wherein, prior to creation of the customer-specific version of the tool, the identification module identifies the desired encryption algorithm for the digital certificate by at least one of:

ascertaining the desired encryption algorithm for the digital certificate from the customer's purchase history; and

requesting and receiving, from the customer, an identification of the desired encryption algorithm for the digital certificate in response to receiving at least one of:

a request from the customer to purchase the digital certificate; and

a request from the customer to download the tool.

14. The system of claim 9 , wherein, prior to creation of the customer-specific version of the tool, the identification module identifies the desired certificate authority for the digital certificate by at least one of:

ascertaining the desired certificate authority from a web portal chosen by the customer when submitting the request for the tool; and

ascertaining the desired certificate authority from a version of the tool requested by the customer.

15. The system of claim 9 , wherein, upon creation of the digital certificate:

the identification module identifies an additional request from the customer for an additional tool for installing the digital certificate;

the tool creation module creates, in response to the additional request, a customer-specific version of the additional tool that is unique to the customer and that includes the digital certificate;

the tool configuration module configures the customer-specific version of the additional tool to install the digital certificate using the included digital certificate; and

the communication module provides the customer-specific version of the additional tool to the customer to enable the customer to install, using the customer-specific version of the additional tool, the digital certificate without having to manually locate the digital certificate.

16. The system of claim 15 , wherein the tool for generating the certificate signing request and the additional tool for installing the digital certificate comprise the same tool.

17. A non-transitory computer-readable-storage medium comprising one or more computer-readable instructions that, when executed by at least one processor of a computing device, cause the computing device to:

identify a request from a customer for a tool for generating a certificate signing request for a digital certificate;

create, in response to the request, a customer-specific version of the tool that is unique to the customer by injecting information that is necessary to generate the certificate signing request into an executable file of the customer-specific version of the tool, wherein the information:

uniquely identifies the customer; and

identifies at least one of a desired encryption algorithm for the digital certificate and a desired certificate authority for the digital certificate;

configure the customer-specific version of the tool to generate the certificate signing request using the injected information; and

provide, to the customer, the customer-specific version of the tool that already contains the injected information necessary to generate the certificate signing request to enable the customer to generate, using the customer-specific version of the tool, the certificate signing request without having to manually provide the injected information.

18. The non-transitory computer-readable-storage medium of claim 17 , wherein the one or more computer-readable instructions further cause the computing device to identify, prior to creating the customer-specific version of the tool, the information that uniquely identifies the customer by at least one of:

retrieving at least a portion of the information that uniquely identifies the customer from a customer database; and

requesting and receiving, from the customer, the information that uniquely identifies the customer in response to receiving at least one of:

a request from the customer to purchase the digital certificate; and

a request from the customer to download the tool.

19. The non-transitory computer-readable-storage medium of claim 17 , wherein the one or more computer-readable instructions further cause the computing device to identify, prior to creating the customer-specific version of the tool, the desired encryption algorithm for the digital certificate by at least one of:

ascertaining the desired encryption algorithm for the digital certificate from the customer's purchase history; and

requesting and receiving, from the customer, an identification of the desired encryption algorithm for the digital certificate in response to receiving at least one of:

a request from the customer to purchase the digital certificate; and

a request from the customer to download the tool.

20. The non-transitory computer-readable-storage medium of claim 17 , wherein the one or more computer-readable instructions further cause the computing device to identify, prior to creating the customer-specific version of the tool, the desired certificate authority for the digital certificate by at least one of:

ascertaining the desired certificate authority from a web portal chosen by the customer when submitting the request for the tool; and

ascertaining the desired certificate authority from a version of the tool requested by the customer.

Assignments (11)
ASSIGNMENT OF SECURITY INTERESTS IN INTELLECTUAL PROPERTY (FIRST LIEN), RECORDED ON OCTOBER 16, 2019 AT REEL 050741 FRAME 0918 Recorded Sep 24, 2025
From: UBS AG, STAMFORD BRANCH, AS SUCCESSOR TO CREDIT SUISSE AG, CAYMAN ISLANDS BRANCH, AS RESIGNING AGENT
To: HPS INVESTMENT PARTNERS, LLC, AS SUCCESSOR AGENT
Reel/Frame 072947/0157 →
SECOND LIEN NOTICE OF SUCCESSION OF AGENCY Recorded Jul 30, 2025
From: CREDIT SUISSE AG, CAYMAN ISLANDS BRANCH, AS PRIOR AGENT
To: UBS AG, STAMFORD BRANCH, AS SUCCESSOR AGENT
Reel/Frame 072300/0068 →
ASSIGNMENT OF INTELLECTUAL PROPERTY SECURITY AGREEMENT Recorded Feb 19, 2021
From: JEFFERIES FINANCE LLC, AS EXISTING AGENT
To: CREDIT SUISSE AG, CAYMAN ISLANDS BRANCH, AS SUCCESSOR AGENT
Reel/Frame 055345/0042 →
RELEASE OF FIRST LIEN SECURITY INTEREST IN PATENTS Recorded Oct 17, 2019
From: UBS AG, STAMFORD BRANCH, AS COLLATERAL AGENT
To: DIGICERT, INC.; GEOTRUST, LLC
Reel/Frame 050746/0973 →
RELEASE OF SECOND LIEN SECURITY INTEREST IN PATENTS Recorded Oct 17, 2019
From: UBS AG, STAMFORD BRANCH, AS COLLATERAL AGENT
To: DIGICERT, INC.; GEOTRUST, LLC
Reel/Frame 050747/0001 →
SECOND LIEN INTELLECTUAL PROPERTY SECURITY AGREEMENT Recorded Oct 16, 2019
From: DIGICERT, INC.
To: JEFFERIES FINANCE LLC, AS COLLATERAL AGENT
Reel/Frame 050741/0899 →
FIRST LIEN INTELLECTUAL PROPERTY SECURITY AGREEMENT Recorded Oct 16, 2019
From: DIGICERT, INC.
To: CREDIT SUISSE AG, CAYMAN ISLANDS BRANCH, AS COLLATERAL AGENT
Reel/Frame 050741/0918 →
FIRST LIEN PATENT SECURITY AGREEMENT Recorded Nov 3, 2017
From: DIGICERT, INC.
To: UBS AG, STAMFORD BRANCH, AS COLLATERAL AGENT
Reel/Frame 044681/0556 →
SECOND LIEN PATENT SECURITY AGREEMENT Recorded Nov 3, 2017
From: DIGICERT, INC.
To: UBS AG, STAMFORD BRANCH, AS COLLATERAL AGENT
Reel/Frame 044710/0529 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Oct 31, 2017
From: SYMANTEC CORPORATION
To: DIGICERT, INC.
Reel/Frame 044344/0650 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Sep 18, 2013
From: TYTULA, ANDREW; SINGAL, PADAM; VERMA, ISHITA
To: SYMANTEC CORPORATION
Reel/Frame 031231/0590 →