Abstract: Technologies are provided for tracking learning progress of an end user of a cloud computing platform when the end user is not registered with an external learning platform that provides an external learning application. In response to the end user interacting with virtual learning entities provided at the cloud computing platform, learning progress information with respect to the external learning application is generated. When a user service of the external learning platform receives a request to persist the learning progress information for the end user, the user service can determine whether a corresponding user account exists at the external learning platform that corresponds to the end user. If a corresponding user account does not exist, the user service can automatically provision an escrow user account that is associated with the end user. The escrow user account persists the learning progress information of the end user.

Abstract: Methods, systems, and devices for distributed caching of encrypted encryption keys are described. Some multi-tenant database systems may support encryption of data records. To efficiently handle multiple encryption keys across multiple application servers, the database system may store the encryption keys in a distributed cache accessible by each of the application servers. To securely cache the encryption keys, the database system may encrypt (e.g., wrap) each data encryption key (DEK) using a second encryption key (e.g., a key encryption key (KEK)). The database system may store the DEKs and KEKs in separate caches to further protect the encryption keys. For example, while the encrypted DEKs may be stored in the distributed cache, the KEKs may be stored locally on application servers. The database system may further support “bring your own key” (BYOK) functionality, where a user may upload a tenant secret or tenant-specific encryption key to the database.

Abstract: A system and method for providing a means securities syndication and investment promotion comprised of a system server, an issuer device, and a client device. Disclosures are appended to the end of relevant content, such as investor statements. The disclosures are generated at one or more issuer device. The disclosures are selected based on the relevant content and target audience. The relevant content and disclosures are then transmitted to the target audience.

Abstract: Technologies are provided for integrating learning data provided by an external learning platform (ELP) to create a custom learner experience within a context of an application provided by a cloud computing platform (CCP). The system can include the CCP, the ELP, learner APIs that expose a common learning data schema on the CCP, and a user interface platform (UIP). The UIP can include a compiler that transforms source code of UICs of a componentized learner user interface for usage on the CCP, and a bundler that generates a package of UI components (UICs) that are compatible for usage on the CCP. The UICs are specific to the learning data schema shared with the learner APIs. The UIP exports the package to the CCP, which composes the learning data provided via learner APIs and UICs from the package to provide the custom learner experience within the context of the application.

Abstract: Technologies are provided for tracking learning progress of an end user of a cloud computing platform when the end user is not registered with an external learning platform that provides an external learning application. In response to the end user interacting with virtual learning entities provided at the cloud computing platform, learning progress information with respect to the external learning application is generated. The interaction by the end user takes place in the context of an application provided by the cloud computing platform while in an active web session. The virtual learning entities represent content of the external learning application (e.g., learning content and contextual user information of the external learning application). When a user service of the external learning platform receives a request to persist the learning progress information for the end user, the user service can determine whether a corresponding user account (e.g.

Abstract: Methods, systems, and devices for distributed caching of encrypted encryption keys are described. Some multi-tenant database systems may support encryption of data records. To efficiently handle multiple encryption keys across multiple application servers, the database system may store the encryption keys in a distributed cache accessible by each of the application servers. To securely cache the encryption keys, the database system may encrypt (e.g., wrap) each data encryption key (DEK) using a second encryption key (e.g., a key encryption key (KEK)). The database system may store the DEKs and KEKs in separate caches to further protect the encryption keys. For example, while the encrypted DEKs may be stored in the distributed cache, the KEKs may be stored locally on application servers. The database system may further support “bring your own key” (BYOK) functionality, where a user may upload a tenant secret or tenant-specific encryption key to the database.

Abstract: Methods, systems, and devices for distributed caching of encrypted encryption keys are described. Some multi-tenant database systems may support encryption of data records. To efficiently handle multiple encryption keys across multiple application servers, the database system may store the encryption keys in a distributed cache accessible by each of the application servers. To securely cache the encryption keys, the database system may encrypt (e.g., wrap) each data encryption key (DEK) using a second encryption key (e.g., a key encryption key (KEK)). The database system may store the DEKs and KEKs in separate caches to further protect the encryption keys. For example, while the encrypted DEKs may be stored in the distributed cache, the KEKs may be stored locally on application servers. The database system may further support “bring your own key” (BYOK) functionality, where a user may upload a tenant secret or tenant-specific encryption key to the database.

Abstract: Methods, systems, and devices for distributed caching of encrypted encryption keys are described. Some multi-tenant database systems may support encryption of data records. To efficiently handle multiple encryption keys across multiple application servers, the database system may store the encryption keys in a distributed cache accessible by each of the application servers. To securely cache the encryption keys, the database system may encrypt (e.g., wrap) each data encryption key (DEK) using a second encryption key (e.g., a key encryption key (KEK)). The database system may store the DEKs and KEKs in separate caches to further protect the encryption keys. For example, while the encrypted DEKs may be stored in the distributed cache, the KEKs may be stored locally on application servers. The database system may further support “bring your own key” (BYOK) functionality, where a user may upload a tenant secret or tenant-specific encryption key to the database.