Abstract: A system having a content management system (CMS) and an edge node of a content delivery network is provided. The CMS and edge node are configured to perform a method that includes sharing a server secret between the CMS and the edge node and using, by the CMS, the server secret to generate a signing key. The signing key includes a signing secret generated using the server secret. The signing key is transmitted to a client system, and the client system receives a request for a content asset from a user device and authorizes said user device for access to the content asset. The client system uses the signing key to generate a signed URL for the content asset, and the user device is redirected to the signed URL. Responsive to receiving, by the edge node, the signed URL from the user device, the method proceeds to validating the signed URL by the edge node. Validating the signed URL uses the server secret to rederive the signing secret based on the signed URL.

Abstract: A method performed by a content management system (CMS) and an edge node of a content delivery network is provided. A server secret is shared between the CMS and the edge node, and CMS uses the server secret to generate a signing key which includes a signing secret generated using the server secret. The signing key is transmitted to a client system. The client system receives a request for a content asset from a user device. The client system uses the signing key to generate a signed URL for the content asset, and the user device is redirected to the signed URL. The edge node validates the signed URL using the server secret to rederive the signing secret based on the signed URL. Responsive to successful validation of the signed URL by the edge node, then the content asset is provided from the edge node to the user device.

Abstract: A method for launching content for publication using a content management system (CMS) is provided. Editing of entities is enabled using an editor application associated with the CMS, the editing includes authoring fields for each entity. A selection of a group of entities is received, via a launch interface of the CMS, the selection is for publishing the group of entities. Responsive to the selection, an API call to the CMS is generated, the API call is programmed to trigger initiation of a validation process to validate each entity in the group of entities, wherein the validation process is processed in a draft entity store of the CMS that is created for said validation without requiring separate API calls for each entity in the group of entities.

Abstract: An application framework for interfacing applications with a content management system (CMS), includes: the CMS configured to provide access to create or update a content project via a content management API; providing an interface to enable adding of an APP to the CMS, the APP is configured to provide a service to be used within the CMS; providing, over a network, a web editor of the CMS to access the content project, wherein responsive to execution of the web editor for the content project in a client browser, the APP is launched in an APP runtime environment that is independent of a web editor runtime environment in which the web editor is executed; wherein API calls received from the APP for the content management API of the CMS are automatically run through a security process of the application framework, the security process is configured to apply a checking process to API calls of the APP.

Abstract: Systems and methods for integrating applications with a content management system (CMS) are provided. One method includes providing access to the CMS via a web editor executed on a client browser, which enables creating and editing content associated with each of a plurality of content types of a content project. The method includes receiving selection of an APP to add functionality of the APP to the web editor, and in response, a separate runtime environment for the APP is launched that causes assignment of an identity to the APP. A unique access token is assigned to the APP for making content management API calls to the CMS for creating and editing content of the content project. The separate runtime environment provides for separation of code used for executing the web editor and used for executing the APP, such that a fault, error or malfunction caused by execution of the APP is not attributed to the web editor.