Secure certificate distribution
View Patent ↗Disclosed are various examples of securely distributing certificates to client devices. A uniform resource locator (URL) is sent to a client device, wherein the URL represents an address from which the client device can request a user certificate. A certificate for a registration authority is sent to the client device, wherein the certificate comprises a first public key and a first private key. A certificate signing request (CSR) received from the client device at the URL is decrypted, wherein the CSR is encrypted with the first public key. The CSR is validated based at least in part on the URL sent to the client device. The user certificate is then sent to the client device.
1. A system, comprising:
a computing device comprising a processor and a memory; and
an application stored in the memory of the computing device that, when executed by the processor of the computing device, causes the computing device to at least:
send a uniform resource locator (URL) and a one-time password to a client device, wherein the URL represents an address from which the client device can request a user certificate with the one-time password and the URL comprises a unique identifier for the client device;
send a certificate for a registration authority to the client device, wherein the certificate comprises a first public key and a first private key;
decrypt a certificate signing request (CSR) received from the client device at the URL, wherein the CSR is encrypted with the first public key;
validate the CSR based at least in part on the URL and the one-time password sent to the client device;
encrypt the user certificate with a second public key provided by the client device;
sign the user certificate with the first private key;
send the user certificate to the client device; and
delete the unique identifier from the memory of the computing device.
2. The system of claim 1 , wherein the application, when executed by the processor of the computing device, further causes the computing device to at least request the user certificate from a certificate authority.
3. The system of claim 1 , wherein validation of the CSR is further based at least in part on whether the unique identifier is included in the URL at which the CSR is received.
4. The system of claim 1 , wherein the application, when executed by the processor of the computing device, further causes the computing device to at least send a list of supported operations to the client device.
5. A method, comprising:
sending a uniform resource locator (URL) and a one-time password to a client device, wherein the URL represents an address from which the client device can request a user certificate with the one-time password and the URL comprises a unique identifier for the client device;
sending a certificate for a registration authority to the client device, wherein the certificate comprises a first public key and a first private key;
decrypting a certificate signing request (CSR) received from the client device at the URL, wherein the CSR is encrypted with the first public key;
validating the CSR based at least in part on the URL and the one-time password sent to the client device;
encrypting the user certificate with a second public key provided by the client device;
signing the user certificate with the first private key;
sending the user certificate to the client device; and
deleting the unique identifier from a memory of the computing device.
6. The method of claim 5 , further comprising requesting the user certificate from a certificate authority.
7. The method of claim 5 , wherein validating the CSR is further based at least in part on whether the unique identifier is included in the URL at which the CSR is received.
8. The method of claim 5 , further comprising sending a list of supported operations to the client device.
9. A non-transitory computer-readable medium storing a plurality of computer instructions executable by a computing device, the plurality of computer instructions being configured to cause the computing device to at least:
send a uniform resource locator (URL) and a one-time password to a client device, wherein the URL represents an address from which the client device can request a user certificate with the one-time password and the URL comprises a unique identifier for the client device;
send a certificate for a registration authority to the client device, wherein the certificate comprises a first public key and a first private key;
decrypt a certificate signing request (CSR) received from the client device at the URL, wherein the CSR is encrypted with the first public key;
validate the CSR based at least in part on the URL and the one-time password sent to the client device;
encrypt the user certificate with a second public key provided by the client device;
sign the user certificate with the first private key;
send the user certificate to the client device; and
delete the unique identifier from the memory of the computing device.
10. The non-transitory computer-readable medium of claim 9 , wherein the plurality of computer instructions are further configured to cause the computing device to at least request the user certificate from a certificate authority.
11. The non-transitory computer-readable medium of claim 9 , wherein validation of the CSR is further based at least in part on whether the unique identifier is included in the URL at which the CSR is received.
12. The non-transitory computer-readable medium of claim 9 , wherein the plurality of computer instructions are further configured to cause the computing device to at least send a list of supported operations to the client device.
13. The non-transitory computer-readable medium of claim 12 , wherein the list of supported operations specifies a type of encryption algorithm.
14. The non-transitory computer-readable medium of claim 12 , wherein the list of supported operations specifies a type of cryptographic hash algorithm.
15. The method of claim 8 , wherein the list of supported operations specifies a type of encryption algorithm.
16. The method of claim 8 , wherein the list of supported operations specifies a type of cryptographic hash algorithm.
17. The method of claim 5 , wherein the user certificate is sent to the client device through a network connection protected by a version of the transport layer security (TLS) protocol.
18. The system of claim 4 , wherein the list of supported operations specifies a type of encryption algorithm.
19. The system of claim 4 , wherein the list of supported operations specifies a type of cryptographic hash algorithm.
20. The system of claim 4 , wherein the user certificate is sent to the client device through a network connection protected by a version of the transport layer security (TLS) protocol.