Vmware, Inc.

Airwatch LLC

Anuj Panwar

Lucas Chen

Rajiv Singh

Raghuram Rajan

Sandeep Naga Kaipu

Kishore Sajja

Siavash James Joorabchian Hawkins

Simon Brooks

Nischit Shetty

Joseph Nickolas Razavian

Yugansh Arora

Examples for validating the identify of an application in an inter-app communication protocol are described. An attestation payload is obtained from a third party attestation service that is executed remotely from a device on which the application is running. The attestation payload can be validated by another application on the device in order to validate the identity of the application providing the attestation payload.

Attestation of application identity for inter-app communications

Aspects of providing single sign on (SSO) sessions are described. An access interval key is generated using an access code as a seed to a key derivative function. The access interval key is encrypted using a public key of an SSO-enabled application to generate an encrypted access interval key for a sign on session. The sign on session is established by storing the encrypted access interval key in a memory location of an SSO session map shared by SSO-enabled applications.

Secure asymmetric key application data sharing

Systems herein can recommend files to users based on meeting information. The system can include a secure email gateway that forwards meeting invitations to an email server and a content server. The system can extract invitee information, meeting timing information, and an attachment from the meeting invitation. During a time period based on the meeting timing information, the content server can cause a managed content application on an invitee's user device to visually identify the attachment as a recommended file. This can allow the user to locate and access relevant files for a meeting, including files that are not attached to the meeting invite, at one location.

Systems for content recommendation based on a meeting invite

To extend a sign on session among applications, an inter-application workflow request can be initiated from a first to a second application. The workflow request can identify one or more memory locations in a shared memory for secure data transfer between the applications. The first application can then monitor the memory locations for the presence of a public key stored in shared memory by the second application in response to the workflow request. Once the public key is present in the shared memory, the first application can retrieve and use it to encrypt an access interval key. The encrypted access interval key can then be stored in the shared memory for retrieval by the second application. The access interval key is associated with a sign on session of the first application, and the second application can retrieve and decrypt it to extend the sign on session to the second application.

Inter-application secure data sharing workflow

To establish a sign on session among single sign on (SSO)-enabled applications, a user can be prompted by an application for an access code. An access interval key can be generated using a key derivative function based on the access code. The access interval key can be considered a session key, and it can be used during a valid SSO session to decrypt a master key stored in a shared memory. In turn, the master key can be used to encrypt and decrypt the contents of the shared memory. To securely distribute the access interval key among the SSO-enabled applications during a current session, individual SSO-enabled applications can each store a public key in the shared memory. The access interval key can then be encrypted, respectively, by the public keys of the SSO-enabled applications and stored in the shared memory to be retrieved securely by the SSO-enabled applications.

Growing community of inventors

Atlanta, GA, United States of America

Anuj Panwar