Restricted application visibility

Patent metadata

Field	Value
Publication number	US-10073720-B2
Application number	US-201514879105-A
Country	US
Kind code	B2
Filing date	Oct 9, 2015
Priority date	Jul 30, 2015
Publication date	Sep 11, 2018
Grant date	Sep 11, 2018

Abstract

Disclosed are various examples of providing a secured application launcher for initiating execution of access-restricted applications. A computer disables a default launch activity alias for a user application, wherein the default launch activity alias comprises a first reference to an application programming interface (API) to initiate execution of the user application. The computer then queries the user application for a presence of a container activity alias provided by the user application, wherein the container activity alias comprises a second reference to the API to initiate execution of the user application. The computer then displays an application icon representing the user application based at least in part on the presence of the container activity alias. The computer then calls the container activity alias for the user application based at least in part on a manipulation of the application icon.

First claim

Therefore, the following is claimed:

1. A system, comprising:
a computing device comprising a processor and a memory;
an application hiding service 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:
remove a default launch activity alias for a user application from a manifest file corresponding to the user application, the default launch activity alias comprising a first reference to an application programming interface (API) to initiate execution of the user application; and

a container 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 message to the application hiding service to remove the default launch activity alias for the user application from the manifest file, wherein the message is sent based on a determination that an identity of a cryptographic key corresponding to a cryptographic signature of the user application matches an identity of an authorized key;
identify, in the manifest file, a container activity alias specified for the user application, wherein the container activity alias comprises a second reference to the API to initiate execution of the user application;
display an application icon representing the user application based at least in part on the container activity alias; and

call the container activity alias for the user application based at least in part on a manipulation of the application icon.

2. The system of claim 1 , wherein the container application, when executed by the processor of the computing device, further causes the computing device to at least:
display a container icon; and
display the application icon based at least in part on a manipulation of the container icon.

3. The system of claim 2 , wherein display of the application icon is further based at least in part a receipt of an authorization code by the container application.

4. The system of claim 3 , wherein the authorization code is a figure drawn on a screen of the computing device.

5. The system of claim 1 , wherein the container application, when executed by the processor of the computing device, further causes the computing device to at least display an application container, wherein the application icon is displayed within the application container.

6. The system of claim 1 , wherein the container activity alias is defined in a manifest file associated with the user application.

7. The system of claim 1 , wherein the user application comprises a third-party library that comprises the application hiding service.

8. A computer-implemented method, comprising:
removing a default launch activity alias for a user application from a manifest file corresponding to the user application based on determining that an identity of a cryptographic key corresponding to a cryptographic signature of the user application matches an identity of an authorized key, the default launch activity alias comprising a first reference to an application programming interface (API) to initiate execution of the user application;
identifying, in the manifest file, a container activity alias specified for the user application, wherein the container activity alias comprises a second reference to the API to initiate execution of the user application;
displaying an application icon representing the user application based at least in part on the container activity alias; and
calling the container activity alias for the user application based at least in part on a manipulation of the application icon.

9. The method of claim 8 , further comprising:
displaying a container icon; and
displaying the application icon based at least in part on a manipulation of the container icon.

10. The method of claim 9 , further comprising:
receiving an authorization code; and
wherein displaying the application icon is further based at least in part on receiving the authorization code.

11. The method of claim 10 , wherein the authorization code comprises a personal identification number (PIN).

12. The method of claim 10 , wherein the authorization code is a figure drawn on a screen of the computing device.

13. The method of claim 8 , further comprising displaying an application container, wherein the application icon is displayed within the application container.

14. The method of claim 8 , wherein the container activity alias is defined in a manifest file associated with the user application.

15. 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:
remove a default launch activity alias for a user application from a manifest file corresponding to the user application based on a determination that an identity of a cryptographic key corresponding to a cryptographic signature of the user application matches an identity of the authorized key, the default launch activity alias comprising a first reference to an application programming interface (API) to initiate execution of the user application;
identify, in the manifest file, a container activity alias specified for the user application, wherein the container activity alias comprises a second reference to the API to initiate execution of the user application;
display an application icon representing the user application based at least in part on the container activity alias; and
call the container activity alias for the user application based at least in part on a manipulation of the application icon.

16. The non-transitory computer-readable medium of claim 15 , wherein the plurality of computer instructions are further configured to cause the computing device to at least:
display a container icon; and
display the application icon based at least in part on a manipulation of the container icon.

17. The non-transitory computer-readable medium of claim 16 , wherein display of the application icon is further based at least in part a receipt of an authorization code by the container application.

18. The non-transitory computer-readable medium of claim 17 , wherein the authorization code is a figure drawn on a screen of the computing device.

19. The non-transitory computer-readable medium of claim 15 , wherein the plurality of computer instructions are further configured to cause the computing device to at least display an application container, wherein the application icon is displayed within the application container.

20. The non-transitory computer-readable medium of claim 15 , wherein the container activity alias is defined in a manifest file associated with the user application.

Assignees

• Airwatch Llc
• Airwatch Llc

Inventors

• RAMAN B R Anantha
• Sethi Nitin
• Tyagi Subham Kumar
• Sequeira Joel

Classifications

• G06F9/543 Primary

  User-generated data transfer, e.g. clipboards, dynamic data exchange [DDE], object linking and embedding [OLE] · CPC title

• H04L2209/24

  Key scheduling, i.e. generating round keys or sub-keys for block encryption · CPC title

• H04L2209/72

  Signcrypting, i.e. digital signing and encrypting simultaneously · CPC title

• H04L9/3247 Primary

  involving digital signatures · CPC title

• H04L9/3226

  using a predetermined code, e.g. password, passphrase or PIN (network architectures or network communication protocols for supporting authentication of entities using passwords in a packet data network H04L63/083) · CPC title