Dynamic certificate generation on a certificate authority cloud
View Patent ↗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.
1. A method for updating a digital certificate, the method comprising:
monitoring a certificate profile and a first key pair, each used to generate a first certificate, to detect a change in the certificate profile, the certificate profile including a plurality of digital certificate attributes for generating a digital certificate by a certificate authority (CA);
detecting a change in the certificate profile, wherein the change is to at least a first attribute in the plurality of digital certificate attributes, wherein the change in the certificate profile is made by a user;
in response to the detected change in the certificate profile:
generating a second key pair, and
sending a request to the CA to generate a second certificate based on the changed certificate profile, wherein the request includes a second public key associated with the second key pair, a server identifier, and a profile identifier associated with the changed certificate profile, and wherein attributes of the second certificate reflect the detected change to the at least the first attribute;
receiving the second certificate from the CA; and
deploying the second certificate on a server in place of the first certificate.
2. The method of claim 1 , wherein the change in the certificate profile modifies one or more subject alternative names (SANs) named in the first certificate.
3. The method of claim 1 , further comprising:
upon determining the second certificate has expired, sending the first public key, the server identifier, and the profile identifier to the CA; and
receiving a third certificate that includes the first public key from the CA; and
deploying the third certificate on the server in place of the second certificate.
4. A non-transitory computer-readable storage medium storing instructions, which, when executed on a processor, performs an operation for updating a digital certificate, the operation comprising:
monitoring a certificate profile and a first key pair, each used to generate a first certificate, to detect a change in the certificate profile, the certificate profile including a plurality of digital certificate attributes for generating a digital certificate by a certificate authority (CA);
detecting a change in the certificate profile, wherein the change is to at least a first attribute in the plurality of digital certificate attributes, wherein the change in the certificate profile is made by a user;
in response to the detected change in the certificate profile:
generating a second key pair, and
sending a request to the CA to generate a second certificate based on the changed certificate profile, wherein the request includes a second public key associated with the second key pair, a server identifier, and a profile identifier associated with the changed certificate profile, and wherein attributes of the second certificate reflect the detected change to the at least the first attribute;
receiving the second certificate from the CA; and
deploying the second certificate on a server in place of the first certificate.
5. The computer-readable storage medium of claim 4 , wherein the change in the certificate profile modifies one or more subject alternative names (SANs) named in the first certificate.
6. The computer-readable storage medium of claim 4 , wherein the operation further comprises:
upon determining the second certificate has expired, sending the first public key, the server identifier, and the profile identifier to the CA; and
receiving a third certificate signing the first public key from the CA; and
deploying the third certificate on the server in place of the second certificate.
7. A system, comprising:
a processor; and
a memory hosting an application, which, when executed on the processor, performs an operation for updating a digital certificate, the operation comprising:
monitoring a certificate profile and a first key pair, each used to generate a first certificate, to detect a change in the certificate profile, the certificate profile including a plurality of digital certificate attributes for generating a digital certificate by a certificate authority (CA);
detecting a change in the certificate profile, wherein the change is to at least a first attribute in the plurality of digital certificate attributes, wherein the change in the certificate profile is made by a user;
in response to the detected change in the certificate profile:
generating a second key pair, and
sending a request to the CA to generate a second certificate based on the changed certificate profile, wherein the request includes a second public key associated with the second key pair, a server identifier, and a profile identifier associated with the changed certificate profile, and wherein attributes of the second certificate reflect the detected change to the at least the first attribute,
receiving the second certificate from the CA; and deploying the second certificate on a server in place of the first certificate.
8. The system of claim 7 , wherein the operation further comprises:
upon determining the second certificate has expired, sending the first public key, the server identifier, and the profile identifier to the CA; and
receiving a third certificate that includes the first public key from the CA; and
deploying the third certificate on the server in place of the second certificate.