Salesforce, Inc.

Salesforce Com, Inc.

Jayanth Parayil Kumarji

Percy Dara Mehta

Shan-Cheng Ho

Kevin Terusaki

Kshama Lalit Thacker

Clinton Tran

Yogesh Patel

Rajkumar Pellakuru

Zhidong Ke

Utsavi Benani

Heng Zhang

Priya Sethuraman

Yifeng Liu

Mugdha Choudhari

Priyadarshini Mitra

Madhav Vaidyanathan

Evan Jiang

Birva Joshi

Nishkam Agrawal

Various techniques and mechanisms for sharing remote resources among a trusted group are disclosed. A credential management agent utilizes a resource credential for a first user to access a secure resource corresponding to the first user for a second user by at least validating a second user and validating a consent of the first user to allow the second user to access the secure resource using the resource credential for the first user. The secure resource resides on a remote server system accessible via one or more application program interfaces (APIs). A platform management agent provides an interface for shared resource-agnostic credential sharing. The platform management agent validates credentials for the second user as belonging to a trusted group and forwards a request for access to the secure resource for the second user to the credential management agent. In response to receiving the resource credential for the first user to access the secure resource, the platform management agent accesses the secure resource on behalf of the second user to allow the second user to utilize the secure resource.

Techniques and architectures for sharing remote resources among a trusted group of users

A method and system uses a test cloud system for monitoring cloud to cloud performance. The method includes initiating a first trust relationship by the test cloud system with a first target cloud system, receiving a success indicator for the trust relationship, in response to the first target cloud verifying the test cloud system is whitelisted, generating a security token using a private key of the test cloud system, and invoking a function of an application programming interface of the first target cloud using the security token to validate functionality of the function of the application programming interface of the first target cloud.

Cloud to cloud test set up for authentication and monitoring

A system and method for rotating private encryption keys for tenants of a database system has been developed. First, three separate public-private encryption keys are generated for a tenant of the database system. The three separate private encryption keys for the tenant are then stored in cloud-based storage. A defined cadence is created to rotate the private encryption keys for the tenant. The three separate private encryption keys for the tenant are defined as a a past private key, a present private key and a future private key. Next, the public encryption key is stored for the tenant in a global tenant directory. The present private key and the public encryption key are retrieved to encrypt and decrypt data from the tenant. The three separate private encryption keys are rotated at the defined cadence, where the past private key is discarded, the present private key becomes a new past private key, the future private key becomes a new present private key, and a new future private key is generated. The new past private key, the new present private key and the new future private key for the tenant are then stored in cloud-based storage.

Centrally rotating private/public encryption keys in a large scale system

The techniques may include maintaining a thread of events for a plurality of users, where each element of the thread corresponds to an event/activity and includes at least a next field that includes a first subset of the plurality of users and a previous field that includes a second subset of the plurality of users. These techniques may allow new events to be quickly added and prior elements may be updated to reflect the addition. Further, the thread elements may allow the thread to be quickly traversed to identify queried information such that the information may be displayed to a user.

User specific event threading

Disclosed are some implementations of systems, apparatus, methods and computer program products for tracking electronic mail (email) events. Upon generating an email, a database entry including an email identifier associated the email is stored. A notification received from a client device is processed, where the notification indicates that the email associated with the email identifier has been opened. Responsive to processing the notification, the database entry associated with the email is identified using the email identifier and event information of the database entry is stored or updated to indicate that the email has been opened. The database entry associated with the email identifier is updated to include attributes of the email, where the attributes include a recipient identifier identifying a recipient of the email. Status information associated with the email may be provided using the database entry, where the status information indicates that the recipient has opened the email.

Tracking premature events in electronic message processing

Growing community of inventors

Burlingame, CA, United States of America

Jayanth Parayil Kumarji