Search Results

Mitigating the OWASP Top 10

An explanation of how Cloud CMS addresses each of the Top 10 OWASP topics: Mitigating-the-OWASP-Top-10.pdf

Score: 6.369463

API / Integrations / Amazon SNS

Amazon SNS The Amazon Simple Notification Service (SNS) is a fast, flexible, fully managed pub-sub messaging service. Use it as a cloud-based mobile app notification service to send push notifications, email, and SMS messages; or as an enterprise-messaging infrastructure. Amazon SNS provides support for Push Notification of messages as well as distribution of messages to custom HTTP endpoints or via conventional SMS, email and other messaging channels. Cloud CMS API Cloud CMS connects to Amazon

Score: 5.9764667

API / Actions / Start Workflow

Start Workflow ID: startWorkflow Starts a workflow with the given node placed into the payload. Configuration Property Type Required Default Description model text true The ID of the workflow model to be used. swimlanes object false Identifies principals to be assigned into workflow swimlanes. The structure is: { "swimlane1": ["domainId1/principalId1"], "swimlane2": ["domainId2/principalId2"] } runtime object false Allows for manual specification of runtime properties including applica

Score: 5.657179

API / Integrations / Amazon SQS

Amazon SQS The Amazon Simple Queue Service (SQS) is a fast, reliable, scalable, fully managed message queuing service. Amazon SQS makes it simple and cost-effective to decouple the components of a cloud application. You can use Amazon SQS to transmit any volume of data, at any level of throughput, without losing messages or requiring other services to be always available. Cloud CMS Application Server The Cloud CMS Application Server is a middle-tier cluster that sits between your mobile/web appl

Score: 5.550766

Cache invalidation via SNS

At present, Cloud CMS can be configured to publish notifications to Amazon SNS. Thus, to take advantage of this, you'd have to first have an Amazon Web Services account and an SNS topic created. Cloud CMS publishes notifications to it. Your topic can then do anything it wants with these notifications. Your cluster can listen for these events and process messages to invalidate cache. Most commonly, people hook the SNS services to the SQS service for queue-based event management. We've chosen this

Score: 5.4378595

Node Lifecycle Events

First, you configure your tenant with the AWS credentials of an IAM user and a SNS topic ARN that you wish to publish notification events to. This can be on your own AWS account so that you can work with these notifications any way you'd like. The notifications are for a variety of node lifecycle events. The primary one is "node_invalidation" which happens whenever a node's state changes. It's an indication that anyone caching anything downstream might want to reconsider their cache state. In te

Score: 4.931111

API / Workflow / Overview

Overview In explaining workflow, let's first take a look at the following things: Workflow Models Workflow Instances Workflow Tasks Workflow Payload Resources Workflow Comments Workflow History Item Workflow Events Workflow Event Handlers A workflow model is a definition of a workflow consisting of a full set of instructions on how content should be routed between participants or activities on its way toward completion. A workflow model is kind of like a blueprint describing the sequence of step

Score: 4.102914

API / Features / Related

Related QName: f:related This feature is applied internally to nodes that are on the other end of a relator association to indicate that the target node is related to the source node. This feature acts as a marker to tell Cloud CMS to consider the related nodes and the relator association at persistence time so the properties can be managed more efficiently in terms of mapping values from one end of the relationship to the other. There is no need to apply or work with this feature manually. For

Score: 4.087046

UI Guide / Content / Locking

Locking Cloud CMS locking is a "data lock" approach which is a transactional lock is taken out when the write of multiple documents begins. This is a transactional lock in the sense that it blocks other write operations against those documents and fails entirely with rollback if any of the documents fail individually. We have transactional writes for multiple documents. We have a changeset-driven versioning model where each transaction writes onto it's own changeset. N number of documents may wr

Score: 3.997739

API / Features / Knowledge Recipient

Knowledge Recipient QName: f:knowledge-recipient Used internally to identify that a node has received one or more knowledge properties from a source Knowledge Space. These properties exist on the JSON but may have their values overwritten at any time. The indicated properties are not "mastered" on this node but rather receive their values from elsewhere. Any node that is marked as a f:knowledge-recipient will have at least one a:shares-knowledge association binding it back to the source of the p

Score: 3.8224463