Vmware, Inc.

Omnissa, LLC

Hemant Sahani

Lucas Chen

Nicholas Brouillette

Gaurav Arora

Eugene Liderman

Saurav Choudhuri

Aditya Ulman

Nicholas Grivas

Anoop Adur

Jubin Benny

Jason Ruby

Evan H Hurst

Ian Ragsdale

Adam Cianfichi

Kannan Parthasarathy

Simon Brooks

Ashka Vakil

Subrahmanya Kumar Giliyaru

Josh Olson

Dinesh Upreti

Disclosed are various embodiments for determining whether to initiate a remote device wipe in a mobile device management context. In one example, a system comprises a computing device configured to identify a device wipe condition for a client device and determine a wipe policy associated with the device wipe condition. A time for a time delay is initiated for a device wipe action of the client device. A wipe instruction is transmitted to execute the device wipe action based on an expiration of the time delay for the device wipe action.

Intelligent device wipes for mobile device management

Disclosed are various approaches for signing documents using mobile devices. A request is sent to a certificate authority for a signing certificate. The signing certificate is then received from the certificate authority. The signing certificate is then stored in the memory. Next, a file is received from a client application executed by the processor of the computing device. Then, the file is signed with the signing certificate to create a signed file. The signed file is then returned to the client application.

Document signing system for mobile devices

Examples for determining access to restricted features of an application are disclosed. A current working status of a user account and an access policy can be analyzed to determine whether access to the restricted feature should be granted or denied. The functionality can be provided by a library bundled within an application.

Restricting access to application functionality based upon working status

Disclosed are various approaches for providing touchless visitor management. A visitor can complete a visitor registration process using a client device of the visitor and obtain a virtual badge credential to a visitor's device. A physical access control system credential as well as a visitor badge can also be obtained to the visitor's device.

Touchless visitor management

Methods and systems are described for analyzing and attesting physical access to a location. In an example, an administrator can create a survey for users in an organization. The survey can be sent to a user device as a notification. The user can complete the survey, and the user's physical access rights can be determined based on the survey answers. When the user attempts to gain access to a location of the organization, the user can provide a digital access badge. The digital access badge can be mapped to the user's access permissions. The user can be granted or denied access depending on whether the user answered the survey and, if answered, what answers the user provided.

System for analyzing and attesting physical access

Examples described herein include systems and methods for management of contextual notifications on user devices. Entities can be categorized as VIP status based on scoring profiles sent from a management server to the user device. Applications on the user device can implement an SDK that reads the profiles and sets certain actions to boost scores and others to reduce scores. These local VIP scores can be sent periodically from the user device to the management server. The management server can use them in conjunction with global VIP scores for the same entities to create aggregated VIP information. This can be sent back to the user device, allowing the user device to then visualize different notifications or workflows based on whether an entity's aggregated VIP information exceeds one or more thresholds.

Management of contextual device notifications with VIP rankings

Disclosed are various approaches for encrypting documents using mobile devices. A first application receives, from a second application a file and an identifier of a user account. The first application then sends a request for a certificate to a certificate authority and receives a certificate in response. The file is then encrypted using the certificate, and the encrypted file is returned to the second application. The second application can identify the user account as the recipient of a file. Then, the second application can send an encryption request that includes the identifier of the user account and the file to the first application. In response to the request, the second application receives the encrypted file and then provides the encrypted file to the recipient.

Growing community of inventors

Palo Alto, CA, United States of America

Hemant Sahani