MULTI-PERSONA MANAGEMENT AND DEVICES

• US 20160277387A1
• Filed: 06/02/2016
• Published: 09/22/2016
• Est. Priority Date: 09/16/2013
• Status: Abandoned Application

• Current Assignee: AirWatch LLC (Broadcom, Inc.)
• Original Assignee: AirWatch LLC (Broadcom, Inc.)
• Inventors: Brannon, J. Blake, DeWeese, William, Stuntebeck, Erich
• Application Number:
  US15/171,411
• Publication Number:
  US 20160277387A1
• Time in Patent Office: Days
• US Class Current: 1/1
• CPC Class Codes: G06F 1/1647 including at least an additional display G06F1/1692 takes precedence
• CPC Class Codes: G06F 21/10 Protecting distributed programs or content, e.g. vending or licensing of copyrighted material protection in video systems or pay television H04N7/16 ; Digital rights management [DRM]
• CPC Class Codes: G06F 21/62 Protecting access to data via a platform, e.g. using keys or access control rules
• CPC Class Codes: G06F 21/74 operating in dual or compartmented mode, i.e. at least one secure mode
• CPC Class Codes: G06F 9/4451 User profiles; Roaming
• CPC Class Codes: H04L 63/083 using passwords cryptographic mechanisms or cryptographic arrangements for entity authentication using a predetermined code H04L9/3226
• CPC Class Codes: H04L 63/10 for controlling access to devices or network resources
• CPC Class Codes: H04L 63/20 for managing network security; network security policies in general filtering policies H04L63/0227
• CPC Class Codes: H04W 12/086 using security domains
• CPC Class Codes: H04W 12/37 Managing security policies for mobile devices or for controlling mobile applications

Abstract

Disclosed are various examples for multi-persona management on a client device. In one example, a client device can be configured to maintain multiple personas for a single user where each of the personas includes a unique configuration of the client device. A first one of the personas can include an enterprise persona while a second one of the personas can include a personal persona. Different methods of authentication can result in the client device toggling between the enterprise persona and the personal persona where the client device is managed by a device management service, for example, when the client device is configured in accordance with the enterprise persona.

Claims

1. A non-transitory computer-readable medium for logging a single user into one of a plurality of personas on a client device comprising program instructions that, when executed by at least one hardware processor of the client device, cause the client device to:

maintain the plurality of personas for the single user on the client device, each of the plurality of personas comprising a unique configuration of the client device, wherein a first one of the plurality of personas comprises an enterprise persona and a second one of the plurality of personas comprises a personal persona;

identify an authentication being made on the client device by the single user using one of a first authentication method or a second authentication method;

in response to the first authentication method being used in the authentication, toggle the client device in accordance with the enterprise persona, wherein the client device is managed by a device management service when the client device is toggled in accordance with the enterprise persona; and

in response to the second authentication method being used in the authentication, toggle the client device in accordance with the personal persona, wherein the client device is not managed by the device management service when the client device is toggled in accordance with the personal persona.

2. The non-transitory computer-readable medium of claim 1, wherein maintaining the plurality of personas for the single user on the client device further comprises maintaining a first memory partition for the enterprise persona and a second memory partition for the personal persona, wherein the first memory partition is separate from the second memory partition.

3. The non-transitory computer-readable medium of claim 1, wherein:

the first authentication method comprises scanning a first finger of the single user using a fingerprint reader communicatively coupled to the client device; and

the second authentication method comprises scanning a second finger of the single user using the fingerprint reader communicatively coupled to the client device, the second finger being different than the first finger.

4. The non-transitory computer-readable medium of claim 1, wherein:

the first authentication method comprises detecting entry of a first password provided by the single user in association with the client device; and

the second authentication method comprises detecting entry of a second password provided by the single user in association with the client device, the second password being different than the first password.

5. The non-transitory computer-readable medium of claim 1, wherein the unique configuration comprises at least one of:

a setting, a policy, a rule, or an attribute customized in association with a user environment.

6. The non-transitory computer-readable medium of claim 1, wherein the enterprise persona or the personal persona comprises a virtual separation of at least one hardware component of the client device, wherein the at least one hardware component comprises a hardware processor, a battery, or memory.

7. The non-transitory computer-readable medium of claim 1, wherein the at least one application executable in a client device further comprises program instructions that, when executed by the at least one hardware processor of the client device, cause the client device to limit access to content for at least the enterprise persona based at least in part on a time, a location of the client device, a presence of another device, a software version, or a required component of software.

8. A method for logging a single user into one of a plurality of personas on a client device, comprising:

maintaining the plurality of personas for the single user on the client device, each of the plurality of personas comprising a unique configuration of the client device, wherein a first one of the plurality of personas comprises an enterprise persona and a second one of the plurality of personas comprises a personal persona;

identifying an authentication being made on the client device by the single user using one of a first authentication method or a second authentication method;

in response to the first authentication method being used in the authentication, toggling the client device in accordance with the enterprise persona, wherein the client device is managed by a device management service when the client device is toggled in accordance with the enterprise persona; and

in response to the second authentication method being used in the authentication, toggling the client device in accordance with the personal persona, wherein the client device is not managed by the device management service when the client device is toggled in accordance with the personal persona.

9. The method of claim 8, wherein maintaining the plurality of personas for the single user on the client device further comprises maintaining a first memory partition for the enterprise persona and a second memory partition for the personal persona, wherein the first memory partition is separate from the second memory partition.

10. The method of claim 8, wherein:

the first authentication method comprises scanning a first finger of the single user using a fingerprint reader communicatively coupled to the client device; and

the second authentication method comprises scanning a second finger of the single user using the fingerprint reader communicatively coupled to the client device, the second finger being different than the first finger.

11. The method of claim 8, wherein:

the first authentication method comprises detecting entry of a first personal identification number provided by the single user in association with the client device; and

the second authentication method comprises detecting entry of a second personal identification number provided by the single user in association with the client device, the second personal identification number being different than the first personal identification number.

12. The method of claim 8, wherein the unique configuration comprises at least one of:

a setting, a policy, a rule, or an attribute customized in association with a user environment.

13. The method of claim 8, wherein the enterprise persona or the personal persona comprises a virtual separation of at least one hardware component of the client device, wherein the at least one hardware component comprises a hardware processor, a battery, or memory.

14. The method of claim 8, further comprising limiting access to content for at least the enterprise persona based at least in part on a time, a location of the client device, a presence of another device, a software version, or a required component of software.

15. A system for logging a single user into one of a plurality of personas, comprising:

a client device comprising at least one hardware processor and in data communication with a device management service over a network;

program instructions that, when executed by the client device, cause the client device to;

maintain the plurality of personas for the single user on the client device, each of the plurality of personas comprising a unique configuration of the client device, wherein a first one of the plurality of personas comprises an enterprise persona and a second one of the plurality of personas comprises a personal persona;

identify an authentication being made on the client device by the single user using one of a first authentication method or a second authentication method;

in response to the first authentication method being used in the authentication, toggle the client device in accordance with the enterprise persona, wherein the client device is managed by the device management service when the client device is toggled in accordance with the enterprise persona; and

in response to the second authentication method being used in the authentication, toggle the client device in accordance with the personal persona, wherein the client device is not managed by the device management service when the client device is toggled in accordance with the personal persona.

16. The system of claim 15, wherein maintaining the plurality of personas for the single user on the client device further comprises maintaining a first memory partition for the enterprise persona and a second memory partition for the personal persona, wherein the first memory partition is separate from the second memory partition.

17. The system of claim 15, wherein:

the first authentication method comprises scanning a first finger of the single user using a fingerprint reader communicatively coupled to the client device; and

the second authentication method comprises scanning a second finger of the single user using the fingerprint reader communicatively coupled to the client device, the second finger being different than the first finger.

18. The system of claim 15, wherein:

the first authentication method comprises detecting entry of a first personal identification number provided by the single user in association with the client device; and

the second authentication method comprises detecting entry of a second personal identification number provided by the single user in association with the client device, the second personal identification number being different than the first personal identification number.

19. The system of claim 15, wherein the unique configuration comprises at least one of:

a setting, a policy, a rule, or an attribute customized in association with a user environment.

20. The system of claim 15, wherein the enterprise persona or the personal persona comprises a virtual separation of at least one hardware component of the client device, wherein the at least one hardware component comprises a hardware processor, a battery, or memory.