# US 12,113,907 B2 · Methods and systems for enrolling Device Identifiers (DevIDs) on redundant hardware > Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt - Number: US 12,113,907 B2 - Document ID: US12113907B2 - Status: Granted - Kind: B2 - Application number: 17/808,411 - Filed: 2022-06-23 - Published: 2022-10-13 - Granted: 2024-10-08 - Earliest claimed: 2018-12-21 - Assignees: Hewlett Packard Enterprise Development LP - Applicants: Hewlett Packard Enterprise Development LP - Inventors: Thomas M. Laffey - Web page: https://patentgrep.com/patent/US12113907B2 ## CPC - G06F 21/71: to assure secure computing or processing of information - H04L 9/3234: {involving additional secure or trusted devices, e.g. TPM, smartcard, USB or software token (network architectures or network communication protocols for supporting authentication of entities using an additional device in a packet data network H04L63/0853)} - G06F 21/73: by creating or determining hardware identification, e.g. serial numbers - H04L 9/083: {involving central third party, e.g. key distribution center [KDC] or trusted third party [TTP]} - H04L 9/3265: {using certificate chains, trees or paths; Hierarchical trust model} - H04L 9/3268: {using certificate validation, registration, distribution or revocation, e.g. certificate revocation list [CRL]} - H04L 63/0428: {wherein the data content is protected, e.g. by encrypting or encapsulating the payload} - H04L 63/0823: {using certificates (cryptographic mechanisms or cryptographic arrangements for entity authentication involving certificates H04L9/3263)} - H04L 63/126: {the source of the received data} - H04L 2209/127: Trusted platform modules [TPM] - G06F: ELECTRIC DIGITAL DATA PROCESSING (computer systems based on specific computational models G06N) - H04L: TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION (arrangements common to telegraphic and telephonic communication H04M) ## Abstract Methods and systems for implementing DevID enrollment for hardware redundant Trust Platform Modules (TPMs), are described. A system can include hardware redundancy for management modules, and for TPMs that correspond to each management module. Accordingly, a product can have a dual-TPM configuration, where both modules are associated with the same product. Further, a process that particularly considers the presence of dual-TPMs for creating, issuing, and enrolling DevID certificates is described. The process issues and maintains DevID certificates for each TPM by synchronizing dual sessions that correspond to each TPM. Also, the process accounts for duplicate identification data, for example allowing the certificate authority (CA) to sign certificates for dual-TPMs linked to the same chassis number. The process can include performing validation checks, rendezvous points, and locks to ensure that DevID certificates are successfully issued for each of the dual-TPMs, respectively. ## Claims ### Claim 1 A method comprising: receiving, at a server from a first management module in a network device that comprises redundant management modules including the first management module and a second management module, a first request for a first security certificate, wherein the first request comprises an indication that another transaction for creating another security certificate is expected from another management module of the redundant management modules; in response to receiving the first request, initiating, at the server responsive to the indication, a state that awaits another request for a security certificate from another management module of the redundant management modules; while the server is in the state, receiving, at the server from the second management module, a second request for a second security certificate; determining, by the server, whether a transaction for the second request is related to a transaction for the first request; and in response to determining that the transaction for the second request is related to the transaction for the first request, sending, by the server, the first security certificate to the first management module, and the second security certificate to the second management module. ### Claim 2 (depends on 1) The method of claim 1, wherein the redundant management modules are to use dual trusted platform modules (TPMs) in the network device. ### Claim 3 (depends on 1) The method of claim 1, wherein the second request, references the first request. ### Claim 4 (depends on 1) The method of claim 1, further comprising: determining whether the first security certificate for the first request was successfully signed; and in response to determining that the first security certificate was successfully signed, determining whether the second security certificate for the second request was successfully signed. ### Claim 5 (depends on 4) The method of claim 4, further comprising: in response to determining that the second security certificate was successfully signed, sending the signed first security certificate to the first management module, and sending the signed second security certificate to the second management module. ### Claim 6 (depends on 1) The method of claim 1, wherein the first security certificate is for a first TPM in the network device, and the second security certificate is for a second TPM in the network device. ### Claim 7 (depends on 1) The method of claim 1, wherein both the first security certificate and the second security certificate comprise a same chassis identity for the network device. ### Claim 8 (depends on 7) The method of claim 7, wherein the same chassis identity comprises a same chassis serial number. ### Claim 9 (depends on 7) The method of claim 7, wherein the first security certificate comprises a first key for a cryptographic operation of the first management module, and the second security certificate comprises a second key for a cryptographic operation of the second management module. ### Claim 10 (depends on 1) The method of claim 1, comprising: while the server is in the state, receiving, at the server, a third request for a security certificate; determining, by the server, whether a transaction for the third request is related to the transaction for the first request; and in response to determining that the transaction for the third request is unrelated to the transaction for the first request, continuing to stay in the state. ### Claim 11 A non-transitory machine-readable storage medium comprising instructions that upon execution cause a server to: receive, at the server from a first management module in a network device that comprises redundant management modules including the first management module and a second management module, a first request for a first security certificate, wherein the first request comprises an indication that another transaction for creating another security certificate is expected from another management module of the redundant management modules; in response to receiving the first request, initiate, in response to the indication, a state that awaits another request for a security certificate from another management module of the redundant management modules; while the server is in the state, receive, at the server from the second management module, a second request for a second security certificate; determine whether a transaction for the second request is related to a transaction for the first request; and in response to determining that the transaction for the second request is related to the transaction for the first request, send, from the server, the first security certificate to the first management module, and the second security certificate to the second management module. ### Claim 12 (depends on 11) The non-transitory machine-readable storage medium of claim 11, wherein the first security certificate is a first device identifier DevID) certificate, and the second security certificate is a second DevID certificate. ### Claim 13 (depends on 1) The non-transitory machine-readable storage medium of claim 1, wherein the redundant management modules are to use dual trusted platform modules (TPMs) in the network device, and wherein the first security certificate is for a first TPM in the network device, and the second security certificate is for a second TPM in the network device. ### Claim 14 (depends on 11) The non-transitory machine-readable storage medium of claim 11, wherein the instructions upon execution cause the server further to: create, at the server, the first security certificate and the second security certificate; request signing of the first security certificate and the second security certificate; and receive a response based on the request. ### Claim 15 (depends on 14) The non-transitory machine-readable storage medium of claim 14, wherein the response is from a remote certificate authority (CA). ### Claim 16 (depends on 15) The non-transitory machine-readable storage medium of claim 15, wherein the instructions upon execution cause the server further to: in response to an indication that the first and second security certificates are in error or were not successfully signed by the remote CA, failing the first request and the second request and returning an indication of failure. ### Claim 17 (depends on 16) The non-transitory machine-readable storage medium of claim 16, wherein the instructions upon execution cause the server further to: store the first security certificate and the second security certificate in a database. ### Claim 18 (depends on 11) The non-transitory machine-readable storage medium of claim 11, wherein both the first security certificate and the second security certificate comprise a same chassis identity for the network device. ### Claim 19 A system comprising: a processor; and a non-transitory storage medium storing instructions executable on the processor to: receive, at the system from a first management module in a network device that comprises redundant management modules including the first management module and a second management module, a first request for a first security certificate, wherein the first request comprises an indication that another transaction for creating another security certificate is expected from another management module of the redundant management modules; in response to receiving the first request, initiate, in response to the indication, a state that awaits another request for a security certificate from another management module of the redundant management modules; while the system is in the state, receive, at the system from the second management module, a second request for a second security certificate; determine whether a transaction for the second request is related to a transaction for the first request; and in response to determining that the transaction for the second request is related to the transaction for the first request, send, from the system, the first security certificate to the first management module, and the second security certificate to the second management module. ### Claim 20 (depends on 19) The system of claim 19, wherein the redundant management modules are to use dual trusted platform modules (TPMs) in the network device, and wherein the first security certificate is for a first TPM in the network device, and the second security certificate is for a second TPM in the network device.