IP Library Patent Application 19371734
Patent Application
App. No. 19/371,734

REGISTERING AND UTILIZING A DEVICE USER KEY

Loading inventors, assignments & file history…
Monitor This Case
Get email alerts when status or documents change.
Order Certified Copies
Most orders are placed with the USPTO same day — all within 24 business hours.
Order via The Patent Place →
Pre-filled with this patent's details
Quick Facts
Patent No.
US None
App. No.
19/371,734
Abstract

Mechanisms for resource management are described. A trust anchor for a device may be obtained. A trust anchor for a user may be obtained. A public key of the device that corresponds to a private key stored in a cryptographic component internal to the device may be generated. The public key of the device may be registered, with a service operated by a resource management system, to a combination of the device and user. Registering the public key of the device may include sending, to the service operated by the resource management system, a registration message that indicates the trust anchor for the device, the trust anchor for the user, and the public key of the device.

Claims (58)

1 . A method at a device, comprising:

obtaining first information that asserts an identity of the device;

obtaining second information that asserts an identity of a user of the device;

generating, at a cryptographic component internal to the device, a public key of the device that corresponds to a private key of the device stored in the cryptographic component;

registering, with a service of a resource management system that is operated by a party, the public key of the device to a combination of the device and the user, wherein registering the public key of the device comprises:

sending, to the service of the resource management system, a registration message that indicates the first information that asserts the identity of the device, the second information that asserts the identity of the user, and the public key of the device; and

sending, to the service of the resource management system, an access request to request access to a resource, the access request comprising a hash of a string of random characters as a challenge associated with the access request.

2 . The method of claim 1 , wherein the public key is registered by an application of the device, the registration message is sent by the application of the device, or both.

3 . The method of claim 1 , further comprising:

generating, after the public key of the device is generated, the registration message, wherein a payload of the registration message comprises the public key of the device and the second information that asserts the identity of the user; and

signing, after the registration message is generated, the payload of the registration message with the first information that asserts the identity of the device.

4 . The method of claim 1 , further comprising:

receiving, based on the public key of the device being registered to the combination of the device and the user at the service of the resource management system, a refresh token.

5 . The method of claim 4 , wherein the refresh token comprises a timestamp indicating when the refresh token was issued, an identifier of the refresh token, an indication of authentication measures used to obtain the refresh token, or any combination thereof.

6 . The method of claim 4 , further comprising:

requesting, after the refresh token is received, access to resources of a second party;

sending, based on the access to the resources of the second party being requested, the refresh token to the service of the resource management system; and

receiving, in response to the refresh token, a session token associated with accessing the resources of the second party.

7 . The method of claim 6 , further comprising:

generating an access request that comprises the refresh token;

signing the access request with the private key of the device to obtain a signed access request; and

sending, after the access request is signed, the signed access request to the service of the resource management system, wherein the refresh token is sent to the service of the resource management system based on sending the signed access request to the service of the resource management system.

8 . The method of claim 7 , further comprising:

generating, based on access to the resources being requested, the string of random characters.

9 . The method of claim 8 , further comprising:

sending, after receiving the session token, the session token and the string of random characters to a second service of the resource management system, wherein the session token comprises the hash of the string of random characters.

10 . The method of claim 6 , further comprising:

receiving, in response to sending the refresh token as part of requesting the session token, a second refresh token with the session token, wherein the refresh token is invalidated based on the second refresh token being issued.

11 . The method of claim 6 , further comprising:

accessing, based on the session token being received and validated by a second service of the resource management system, the resources of the second party.

12 . The method of claim 6 , wherein the session token is signed by a private key of the service of the resource management system.

13 . The method of claim 1 , wherein the first information that asserts the identity of the device comprises a mobile device management certificate, a certificate obtained as a result of a procedure for enrolling the device with a second service of the resource management system, or both.

14 . The method of claim 1 , wherein the second information that asserts the identity of the user comprises an identity token obtained for the user.

15 . The method of claim 1 , further comprising:

enrolling, by an agent of the device, the device with a second service of the resource management system; and

receiving, based on enrolling the device with the second service, a certificate that uniquely identifies the device, wherein the first information that asserts the identity of the device comprises the certificate.

16 . The method of claim 1 , further comprising:

receiving, from a second service of the resource management system, a mobile device management file;

setting configurations of the device in accordance with a mobile device management policy indicated in the mobile device management file; and

receiving, based on setting the configurations, a mobile device management certificate that uniquely identifies the device, wherein the first information that asserts the identity of the device comprises the mobile device management certificate.

17 . The method of claim 1 , further comprising:

sending a request from the user to verify the identity of the user; and

receiving, from a third service of the resource management system, an identity token that uniquely identifies the user, wherein the second information that asserts the identity of the user comprises the identity token.

18 . A method at a device, comprising:

obtaining first information that asserts an identity of the device;

obtaining second information that asserts an identity of a user of the device;

generating, at a cryptographic component internal to the device, a public key of the device that corresponds to a private key of the device stored in the cryptographic component; and

registering, with a service of a resource management system that is operated by a party, the public key of the device to a combination of the device and the user, wherein registering the public key of the device comprises:

sending, to the service of the resource management system, a registration message that indicates the first information that asserts the identity of the device, the second information that asserts the identity of the user, and the public key of the device.

19 . The method of claim 18 , wherein the public key is registered by an application of the device, the registration message is sent by the application of the device, or both.

20 . A device, comprising:

one or more processors; and

one or more memories storing code comprising instructions executable by the one or more processors, individually or collectively, to cause the device to:

obtain first information that asserts an identity of the device;

obtain second information that asserts an identity of a user of the device;

generate, at a cryptographic component internal to the device, a public key of the device that corresponds to a private key of the device stored in the cryptographic component;

register, with a service of a resource management system that is operated by a party, the public key of the device to a combination of the device and the user, wherein, to register the public key of the device, the one or more processors, individually or collectively, cause the device to send, to the service of the resource management system, a registration message that indicates the first information that asserts the identity of the device, the second information that asserts the identity of the user, and the public key of the device; and

send, to the service of the resource management system, an access request to request access to a resource, the access request comprising a hash of a string of random characters as a challenge associated with the access request.