# US 2019/0356651 A1 · Dynamic certificate generation on a certificate authority cloud

> Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt

- Number: US 2019/0356651 A1
- Document ID: US20190356651A1
- Status: Published application
- Kind: A1
- Application number: 16/437,751
- Filed: 2019-06-11
- Published: 2019-11-21
- Earliest claimed: 2013-09-30
- Assignees: DigiCert, Inc.
- Applicants: DigiCert, Inc.
- Inventors: Kokil Bhalerao
- Web page: https://patentgrep.com/patent/US20190356651A1

## CPC

- H04L 63/0823: {using certificates (cryptographic mechanisms or cryptographic arrangements for entity authentication involving certificates H04L9/3263)}
- H04L: TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION (arrangements common to telegraphic and telephonic communication H04M)

## Abstract

Techniques are disclosed for dynamically generating a digital certificate for a customer server. A customer server creates a certificate profile and receives an associated profile identifier from a certificate authority (CA). The customer server installs an agent application received from the CA. The agent application generates a public/private key pair and an identifier associated with the customer server. The agent application sends a signed request to the CA that includes the profile identifier, server identifier, and the public key corresponding to the key pair. Upon receiving the credentials, the CA generates a dynamically updatable certificate. Thereafter, if the customer changes information associated with the certificate (or if external conditions require a change to the certificate, such as a key compromise or change in security standards), the CA may generate an updated certificate based on the certificate profile changes and the public key.

## Claims

### Claim at position 1

1-21. (canceled)

### Claim 22

A method for generating a digital certificate, comprising:
communicating to an agent application installed on a customer computing system associated with a first private key and a first public key a request to generate at least a second private key and a second public key;
receiving a request for a certificate from the agent application, wherein the request includes the second public key and an identifier associated with the customer computing system;
generating a certificate based at least in part on the request for the certificate; and
communicating the certificate to the customer computing system.

### Claim 23 (depends on 22)

The method of claim 22, further comprising:
determining the first private key has been compromised; and
invalidating the first private key and the first public key.

### Claim 24 (depends on 22)

The method of claim 22, wherein the communicating the request is based at least in part on a determination that the first private key and the first public key has expired.

### Claim 25 (depends on 22)

The method of claim 22, wherein the request further includes a profile identifier associated with a certificate profile.

### Claim 26 (depends on 25)

The method of claim 25, wherein the communicating the request is responsive to detecting at least one change in the certificate profile.

### Claim 27 (depends on 26)

The method of claim 26, wherein the certificate profile includes at least one of a common name, a subject name, a signature algorithm identification, usage restrictions, credentials, a user identifier, or a password, and wherein the detecting the at least one change in the certificate profile comprises detecting a change in at least one of the common name, the subject name, the signature algorithm identification, the usage restrictions, the credentials, the user identifier, or the password.

### Claim 28 (depends on 25)

The method of claim 25, wherein the certificate includes the certificate profile and the second public key.

### Claim 29 (depends on 22)

The method of claim 22, further comprising associating the customer computing system with the second public key based at least in part on the receiving the request for the certificate.

### Claim 30 (depends on 22)

The method of claim 22, wherein the request for the certificate is signed by the second private key.

### Claim 31 (depends on 22)

The method of claim 22, wherein the agent application generates the second private key and the second public key responsive to the receiving the request.

### Claim 32 (depends on 22)

The method of claim 22, wherein the communicating the certificate to the customer computing system comprises communicating the certificate to the customer computing system using the second public key.

### Claim 33 (depends on 22)

The method of claim 22, wherein the method is performed by a certificate authority.

### Claim 34

A non-transitory, computer-readable storage media storing instructions, which, when executed on a processor, performs an operation for generating a digital certificate, the operation comprising:
communicating to an agent application installed on a customer computing system associated with a first private key and a first public key a request to generate at least a second private key and a second public key;
receiving a request for a certificate from the agent application, wherein the request includes the second public key and an identifier associated with the customer computing system;
generating a certificate based at least in part on the request for the certificate; and
communicating the certificate to the customer computing system.

### Claim 35 (depends on 34)

The non-transitory, computer-readable storage media of claim 34, further comprising:
determining that the first private key has been compromised; and
invalidating the first private key and the first public key.

### Claim 36 (depends on 34)

The non-transitory, computer-readable storage media of claim 34, wherein the communicating the request is based at least in part on a determination that at least one of the first private key or the first public key has expired.

### Claim 37 (depends on 34)

The non-transitory, computer-readable storage media of claim 34, wherein the request further includes a profile identifier associated with a certificate profile, wherein the communicating the request is responsive to detecting at least one change in the certificate profile.

### Claim 38 (depends on 37)

The non-transitory, computer-readable storage media of claim 37, wherein the certificate profile includes at least one of a common name, a subject name, a signature algorithm identification, usage restrictions, credentials, a user identifier, or a password, and wherein the detecting the at least one change in the certificate profile comprises detecting a change in at least one of the common name, the subject name, the signature algorithm identification, the usage restrictions, the credentials, the user identifier, or the password.

### Claim 39

A system, comprising:
a processor and a memory hosting an application, which, when executed on the processor, performs an operation for generating a digital certificate, the operation comprising:
communicating to an agent application installed on a customer computing system associated with a first private key and a first public key a request to generate at least a second private key and a second public key;
receiving a request for a certificate from the agent application, wherein the request includes the second public key and an identifier associated with the customer computing system;
generating a certificate based at least in part on the request for the certificate; and
communicating the certificate to the customer computing system.

### Claim 40 (depends on 39)

The system of claim 39, wherein the request further includes a profile identifier associated with a certificate profile, wherein the certificate profile includes at least one of a common name, a subject name, a signature algorithm identification, usage restrictions, credentials, a user identifier, or a password, wherein the communicating the request is responsive to detecting at least one change in the certificate profile, and wherein the detecting the at least one change in the certificate profile comprises detecting a change in at least one of the common name, the subject name, the signature algorithm identification, the usage restrictions, the credentials, the user identifier, or the password.
