Abstract: Techniques for securing access to protected resources are provided. In the method and apparatus, an access key and proof of successful completion of a first authentication is obtained in connection to a request. The proof of completion of the first authentication and the access key are verified. The access key is then used to generate a determination that information in the access key indicates that a second authentication was successfully completed prior to allowing the request to be fulfilled.

Abstract: To ensure that clients use the most current versions of schemas and provide requests to particular Application Programming Interfaces (APIs) in a desired order, identifiers associated with resources may be used to determine client requests that comply with desired schemas and API interactions. When a request to access a first resource is received, a link to a second resource and an identifier may be provided. When a request to access the second resource is received, if the identifier associated with the request is absent or does not match the expected identifier, the request may be denied without using computational resources to process the request. Identifiers may include strings included in Uniform Resource Identifiers (URIs) or query parameters. Identifiers may also include modified field names, arrangements, or other characteristics of schemas associated with the requests. Schemas of received requests may be converted to standard schemas to prepare a response.

Abstract: Techniques for securing access to protected resources are provided. In the method and apparatus, an access key and proof of successful completion of a first authentication is obtained in connection to a request. The proof of completion of the first authentication and the access key are verified. The access key is then used to generate a determination that information in the access key indicates that a second authentication was successfully completed prior to allowing the request to be fulfilled.

Abstract: Disclosed are various embodiments for granting and securing ownership of cross-application digital assets using a blockchain. An asset record is generated in a blockchain. The asset record represents a digital asset being awarded to a user by a first application based on an amount of application-measured effort expended by the user or an achievement earned by the user in engaging with the first application. The digital asset may be usable by the user in the first application and at least one second application.

Abstract: Techniques for controlling the synchronization of data records between servers and client devices include use of configuration data for each client device to control the times at which the current version of server data records is sent to each client device. The configuration data also controls the times at which modified versions of local data records on the client device are sent to the server. The configuration data additionally indicates one or more control actions that are performed if the data record version associated with user input modifying a data record does not match the current version of the server data record. Control actions may include preventing modification of data records, providing notifications to client devices, and providing the current version of server data records to client devices. In some cases, control actions may include permitting certain types of modifications while preventing other types of modifications.

Abstract: Access to Application Programming Interface (API) resources that span multiple categories is facilitated by the addition of labels to at least a subset of the resources. While the resources remain in their original hierarchical categories, the labels are useable to query, access, and manipulate resources that span multiple categories without necessitating use of complex queries or multiple API calls. A label may indicate the category to which a resource belongs. If a first resource includes a link to a second resource, a label for the second resource may indicate the category of the first resource. Labels may also be associated with resources based on specific content types and data values contained with the resource. Use of labels in such a manner enables a body of resources that spans multiple categories to be queried based on categorical relationships as well as the type of data associated with each resource.