# US 12,225,124 B2 · Data center asset onboarding authentication for a data center asset via an onboarding operation > Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt - Number: US 12,225,124 B2 - Document ID: US12225124B2 - Status: Granted - Kind: B2 - Application number: 18/209,436 - Filed: 2023-06-13 - Published: 2024-12-19 - Granted: 2025-02-11 - Earliest claimed: 2023-06-13 - Assignees: Dell Products L.P. - Applicants: Dell Products L.P. - Inventors: Kirk Frey; Ching-Yun Chao - Web page: https://patentgrep.com/patent/US12225124B2 ## CPC - H04L 9/088: {Usage controlling of secret information, e.g. techniques for restricting cryptographic keys to pre-authorized uses, different access levels, validity of crypto-period, different key- or password length, or different strong and weak cryptographic algorithms (network architectures or network communication protocols for using time-dependent keys in a packet data network H04L63/068)} - H04L 9/30: Public key, i.e. encryption algorithm being computationally infeasible to invert or user's encryption keys not requiring secrecy - H04L 41/0806: for initial configuration or provisioning, e.g. plug-and-play - H04L: TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION (arrangements common to telegraphic and telephonic communication H04M) ## Abstract A system, method, and computer-readable medium for performing a data center monitoring and management operation. The data center monitoring and management operation includes: providing the data center asset to a data center asset purchaser; establishing a communication channel between an onboarding system and the data center asset; generating a request to a rendezvous service to generate a shared data center asset secret key for the data center asset; associating the shared data center asset secret key with the data center asset; and, providing authorization for the data center asset to be onboarded when the shared data center asset secret key generated by the rendezvous service matches the shared data center asset secret key associated with the data center asset. ## Claims ### Claim 1 A computer-implementable method for performing a data center monitoring and management operation, comprising: providing the data center asset to a data center asset purchaser; establishing a first communication channel between an onboarding system and the data center asset; establishing a second communication channel between a rendezvous server and the data center asset, the rendezvous server functioning as a rendezvous point between a newly powered-on data center asset and an onboarding service, the rendezvous server executing a trusted rendezvous service, the trusted rendezvous service being implemented to validate and register data center assets; generating a request to the trusted rendezvous service to generate a shared data center asset secret key for the data center asset; associating the shared data center asset secret key with the data center asset; sharing the shared data center asset secret key with the trusted rendezvous service upon receiving a request from the trusted rendezvous service that is encrypted by a public key of the data center asset purchaser; and, providing authorization for the data center asset to be onboarded when the shared data center asset secret key returned by the trusted rendezvous service matches the shared data center asset secret key associated with the data center asset. ### Claim 2 (depends on 1) The method of claim 1, wherein: the establishing the first communication channel between the onboarding system and the data center asset conforms to a Fast Identity Online (FIDO) Alliance FIDO Device Onboard (FDO) specification. ### Claim 3 (depends on 1) The method of claim 1, wherein: the shared data center asset secret key is derived from a public key of the data center asset purchaser. ### Claim 4 (depends on 1) The method of claim 1, further comprising: generating an onboarding request; and, using the shared data center asset secret key to encrypt the onboarding request. ### Claim 5 (depends on 4) The method of claim 4, further comprising: submitting the encrypted onboarding request to the trusted rendezvous service; and, using the encrypted onboarding request when providing authorization for the data center asset to be onboarded. ### Claim 6 (depends on 1) The method of claim 1, wherein: a rendezvous support service communicates with the trusted rendezvous service via a third communication channel between the rendezvous server and the onboarding system. ### Claim 7 A system comprising: a processor; a data bus coupled to the processor; and, a non-transitory, computer-readable storage medium embodying computer program code, the non-transitory, computer-readable storage medium being coupled to the data bus, the computer program code interacting with a plurality of computer operations and comprising instructions executable by the processor and configured for: providing the data center asset to a data center asset purchaser; establishing a first communication channel between an onboarding system and the data center asset; establishing a second communication channel between a rendezvous server and the data center asset, the rendezvous server functioning as a rendezvous point between a newly powered-on data center asset and an onboarding service, the rendezvous server executing a trusted rendezvous service, the trusted rendezvous service being implemented to validate and register data center assets; generating a request to the trusted rendezvous service to generate a shared data center asset secret key for the data center asset; associating the shared data center asset secret key with the data center asset; sharing the shared data center asset secret key with the trusted rendezvous service upon receiving a request from the trusted rendezvous service that is encrypted by a public key of the data center asset purchaser; and, providing authorization for the data center asset to be onboarded when the shared data center asset secret key returned by the trusted rendezvous service matches the shared data center asset secret key associated with the data center asset. ### Claim 8 (depends on 7) The system of claim 7, wherein: the establishing the first communication channel between the onboarding system and the data center asset conforms to a Fast Identity Online (FIDO) Alliance FIDO Device Onboard (FDO) specification. ### Claim 9 (depends on 7) The system of claim 7, wherein: the shared data center asset secret key is derived from a public key of the data center asset purchaser. ### Claim 10 (depends on 9) The system of claim 9, wherein the instructions executable by the processor are further configured for: generating an onboarding request; and, using the shared data center asset secret key to encrypt the onboarding request. ### Claim 11 (depends on 10) The system of claim 10, wherein the instructions executable by the processor are further configured for: submitting the encrypted onboarding request to the trusted rendezvous service; and, using the encrypted onboarding request when providing authorization for the data center asset to be onboarded. ### Claim 12 (depends on 7) The system of claim 7, wherein: a rendezvous support service communicates with the trusted rendezvous service via a third communication channel between the rendezvous server and the onboarding system. ### Claim 13 A non-transitory, computer-readable storage medium embodying computer program code, the computer program code comprising computer executable instructions configured for: providing the data center asset to a data center asset purchaser; establishing a first communication channel between an onboarding system and the data center asset; establishing a second communication channel between a rendezvous server and the data center asset, the rendezvous server functioning as a rendezvous point between a newly powered-on data center asset and an onboarding service, the rendezvous server executing a trusted rendezvous service, the trusted rendezvous service being implemented to validate and register data center assets; generating a request to the trusted rendezvous service to generate a shared data center asset secret key for the data center asset; associating the shared data center asset secret key with the data center asset; and, sharing the shared data center asset secret key with the trusted rendezvous service upon receiving a request from the trusted rendezvous service that is encrypted by a public key of the data center asset purchaser; and, providing authorization for the data center asset to be onboarded when the shared data center asset secret key returned by the trusted rendezvous service matches the shared data center asset secret key associated with the data center asset. ### Claim 14 (depends on 13) The non-transitory, computer-readable storage medium of claim 13, wherein: the establishing the first communication channel between the onboarding system and the data center asset conforms to a Fast Identity Online (FIDO) Alliance FIDO Device Onboard (FDO) specification. ### Claim 15 (depends on 13) The non-transitory, computer-readable storage medium of claim 13, wherein: the shared data center asset secret key is derived from a public key of the data center asset purchaser. ### Claim 16 (depends on 13) The non-transitory, computer-readable storage medium of claim 13, wherein the computer executable instructions are further configured for: generating an onboarding request; and, using the shared data center asset secret key to encrypt the onboarding request. ### Claim 17 (depends on 16) The non-transitory, computer-readable storage medium of claim 16, wherein the computer executable instructions are further configured for: submitting the encrypted onboarding request to the trusted rendezvous service; and, using the encrypted onboarding request when providing authorization for the data center asset to be onboarded. ### Claim 18 (depends on 13) The non-transitory, computer-readable storage medium of claim 13, wherein: a rendezvous support service communicates with the trusted rendezvous service via a third communication channel between the rendezvous server and the onboarding system. ### Claim 19 (depends on 13) The non-transitory, computer-readable storage medium of claim 13, wherein: the computer executable instructions are deployable to a client system from a server system at a remote location. ### Claim 20 (depends on 13) The non-transitory, computer-readable storage medium of claim 13, wherein: the computer executable instructions are provided by a service provider to a user on an on-demand basis.