Self-removal of enterprise app data
Self-removal of enterprise application data (e.g., managed application data) is disclosed. It may be determined that a data removal condition has been satisfied. Based at least in part on the determination, data removal information may be generated for a plurality of applications including a managed set of mobile applications. The data removal information may be provided to at least a first application included in the plurality of applications. The first application may provide the data removal information to a data storage location accessible to at least a second application upon a data removal-related event.
1. A method, comprising:
determining that a data removal condition has been satisfied;
generating, based at least in part on the determination, data removal information for a plurality of applications comprising a managed set of mobile applications;
providing the data removal information to at least a first application of a device included in the plurality of applications, such that the first application provides the data removal information to a data storage location of the device that is accessible to at least a second application of the device upon a data removal-related event, wherein the data removal information at least includes data removal instructions and the second application is capable of at least executing the data removal instructions;
determining whether removal of data from the second application has been interrupted; and
updating a data removal status associated with the second application based on whether removal of data from the second application has been interrupted.
2. The method of claim 1 , further comprising updating the data removal information in the event the removal of data from the second application has been interrupted.
3. The method of claim 1 , further comprising updating the data removal information to include at least an indication indicative of a data removal interruption in the event the removal of data from the second application has been interrupted.
4. The method of claim 1 , further comprising updating the data removal information to include at least an indication indicative of a data removal interruption in the event the removal of data from the second application has been interrupted, wherein the updated data removal information is stored to the data storage location.
5. The method of claim 1 , wherein the data removal status associated with the second application is updated by a library associated with the second application.
6. The method of claim 1 , further comprising:
updating the data removal information in the event the removal of data from the second application has been interrupted; and
detecting by a data removal library associated with an activated application the data removal information.
7. The method of claim 1 , further comprising:
resuming application data removal upon detecting a data removal command included in the data removal information.
8. The method of claim 1 , further comprising:
resuming application data removal upon detecting a data removal command included in the data removal information; and
reinitiating the data removal process associated with the second application in the event the removal of data from the second application is interrupted.
9. The method of claim 1 , wherein the first application includes a management agent that manages one or more applications in the managed set and the second application includes a managed application in the managed set.
10. The method of claim 1 , wherein the first application includes a management agent that manages one or more applications in the managed set and the second application includes a managed application in the managed set, and wherein the data removal-event includes a determination by the management agent that data is to be removed from the plurality of applications.
11. The method of claim 1 , wherein the data removal instructions includes one or more of data removal instructions, identifying information associated with the plurality of applications, a manner of invoking one or more of the plurality of applications, and a data removal status associated with one or more applications in the plurality of applications.
12. The method of claim 1 , wherein determining that the data removal condition has been satisfied includes receiving the data removal information from a device management server.
13. The method of claim 1 , wherein each application in the plurality of applications includes a library configured to remove at least a portion of data associated with the application based at least in part on the data removal information.
14. The method of claim 1 , further comprising:
determining, by an application in the plurality of applications based at least in part on the data removal information, that each application in the plurality of applications has completed data removal.
15. The method of claim 1 , further comprising:
determining, by an application in the plurality of applications based at least in part on the data removal information, that each application in the plurality of applications has completed data removal; and
invoking a management agent associated with the managed set of applications.
16. The method of claim 1 , further comprising:
determining, by an application in the plurality of applications based at least in part on the data removal information, that each application in the plurality of applications has completed data removal;
invoking a management agent associated with the managed set of applications; and
confirming, by the management agent, that data has been removed from each of the plurality of applications.
17. A system, comprising:
a processor; and
a memory coupled with the processor, wherein the memory is configured to provide the processor with instructions which when executed cause the processor to:
determine that a data removal condition has been satisfied;
generate, based at least in part on the determination, data removal information for a plurality of applications comprising a managed set of mobile applications;
provide the data removal information to at least a first application of a device included in the plurality of applications, such that the first application provides the data removal information to a data storage location of the device that is accessible to at least a second application of the device upon a data removal-related event, wherein the data removal information at least includes data removal instructions and the second application is capable of at least executing the data removal instructions;
determine whether removal of data from the second application has been interrupted; and
update a data removal status associated with the second application based on whether removal of data from the second application has been interrupted.
18. The system of claim 17 , wherein the memory is further configured to provide the processor with instructions which when executed cause the processor to: update the data removal information in the event the removal of data from the second application has been interrupted.
19. The system of claim 17 , wherein the memory is further configured to provide the processor with instructions which when executed cause the processor to: resume application data removal upon detecting a data removal command included in the data removal information.
20. A computer program product comprising a tangible non-transitory computer readable storage medium including computer instructions for:
determining that a data removal condition has been satisfied;
generating, based at least in part on the determination, data removal information for a plurality of applications comprising a managed set of mobile applications;
providing the data removal information to at least a first application of a device included in the plurality of applications, such that the first application provides the data removal information to a data storage location of the device that is accessible to at least a second application of the device upon a data removal-related event, wherein the data removal information at least includes data removal instructions and the second application is capable of at least executing the data removal instructions;
determining whether removal of data from the second application has been interrupted; and
updating a data removal status associated with the second application based on whether removal of data from the second application has been interrupted.