Found 58 results for "manual topics authorities"

The search executed in 0.001 seconds

Security

Security Cloud CMS provides two ways to describe access rights to things: Object-level / role-based authorities Team / role-based authorities With object-level / role-based authorities, you assign a principal (either a user or a group) a role against something. For example, you might give Joe the CONSUMER role against a content node. When Joe then interacts with the content node in the future, he will do so with the CONSUMER role which will allow him to "read" the node. With team / role-based au

Score: 24.081905

Security / Authorities

Authorities Every data store and object in Cloud CMS maintains access control lists so that you can finely describe the rights of any principal in the system against it. This lets you finely tune the rights of individual users against data stores and objects down to a single permission. This access control is authority-based which means that it's applied by granting authorities (or roles) that a principal has over an object. Let's buckle down on the terminology for a moment: A Permissioned entit

Score: 15.824444

Features / Propagates Authorities

Propagates Authorities QName: f:propagates-authorities Flags an association as one that propagates inherited authorities from the source to the target. If a parent has authorities assigned to it, those authorities are propagated to the children as masked a:hasRole associations. These associations have inherited set to true and inheritsAssociation set to the association ID being masked. Cloud CMS uses this feature to model propagation of authorities in a containment model within the graph. When y

Score: 13.620783

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: 7.794218

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: 6.588096

Query

Query Cloud CMS provides SQL-like, structured query for all of your content. The platform uses MongoDB under the hood to store the JSON for your content. MongoDB offers a powerful, unmatched query engine so that you can execute complex lookups of your content to support both your editorial and runtime application needs. The platform also offers "composite" query operations which let you layer MongoDB queries on top of Elastic Search DSL searches and traversals around node objects. Cloud CMS auto

Score: 6.292932

Application Server / Services / Broadcast

Broadcast The Broadcast service is responsible for relaying messages to members of the application server cluster. It provides an essential publish and subscription service so that application server members can broadcast messages, receive messages and subscribe to topics and events that occur throughout the system. Essential Configuration { "broadcast": { "enabled": , "type": "", "config": { ...configuration } } } There are two

Score: 6.0466537

API / Data Types / Changeset

Changeset Type changeset Datastore Type repository Supports authorities, permissions, transfer In this sense, a branch can be thought of as a stack of changesets. There is a root changeset (where the branch starts) and a tip changeset (where the branch ends). Everything in-between constitutes the changeset history of the branch. This portion of the API therefore is largely for advanced users. The Cloud CMS API lets you dig in and poke around at the changeset history of branches to do things like

Score: 4.2561707

User Interface / 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.9794421

How does security work in Cloud CMS?

Cloud CMS provides two ways to describe access rights to things: Object-level / role-based authorities Team / role-based authorities With object-level / role-based authorities, you assign a principal (either a user or a group) a role against something. For example, you might give Joe the CONSUMER role against a content node. When Joe then interacts with the content node in the future, he will do so with the CONSUMER role which will allow him to "read" the node. With team / role-based authorities

Score: 3.918157

Modules / Bindings

Bindings Actions Each action supports a binding like this: { "key": "{key}", (required) "title": "{title}", (required) "action": "{action}", "module": "{module}", "iconClass": "{iconClass}", "order": {order}, "allowPermission": [], "rejectPermission": [], "allowAuthority": [], "rejectAuthority": [] } The properties are defined as shown below: Property Type Required Description key string yes a unique key for the me

Score: 3.6319225

API / Data Types / Identity

Identity Type identity Datastore Type directory Supports authorities, permissions, transfer

Score: 3.4924953

API / Data Types / Plan

Plan Type plan Datastore Type registrar Supports authorities, permissions, transfer

Score: 3.4924953

API / Data Types / Settings

Settings Type settings Datastore Type application Supports authorities, permissions, transfer

Score: 3.4924953

API / Data Types / Tenant

Tenant Type tenant Datastore Type registrar Supports authorities, permissions, transfer

Score: 3.4924953

API / Data Types / Archive

Archive Type archive Datastore Type registrar Supports authorities, permissions, transfer TODO

Score: 3.4847887

API / Data Types / Auto Client Mapping

Auto Client Mapping Type autoClientMapping Datastore Type webhost Supports authorities, permissions, transfer

Score: 3.4618719

Actions / Unlock Node

Unlock Node ID: unlockNode Unlocks a node as the current user. The current user must have the lock or the current user must have authorities to remove the lock. Configuration Property Type Required Default Description repositoryId text true The ID of the repository of the node. branchId text true The ID of the branch of the node. nodeId text true The ID of the node.

Score: 3.2549527

Modules / Evaluators

Evaluators Evaluators are used to define conditions that determine whether a block of configuration should be included in the evaluated and merged configuration document. Evaluators work on different aspects of the runtime experience, including: what is being observed who is observed it what URL is being looked at what objects are known about at the time (i.e. observables) what permissions and authorities the current user has over things that are being observed There are many types of evaluators

Score: 3.101534

General / Locking

Locking Cloud CMS supports locking of nodes (or content instances). Locking allows content editorial team members to explicitly block other editors from working on content that they're already working on. When a piece of content is locked by a user, all other users in the project who have access to the piece of content will be prohibited from making modifications. They will be able to read the content but they will not be able to save any modifications. Once the lock is released by the user who

Score: 3.0708134

Role-based security access

You can configure a Cloud CMS project to provide precise, role-based access to content types and content instances. Let's take a look at example of how this is done! Suppose that you have three users - Jim, Dwight and Michael - and two content types (my:article and my:news). We would like things to work like this: Michael is the boss. He is allowed to view, create, edit and delete content content of all types. Dwight is a worker. He is allowed to view, create, edit and delete content of type "my

Score: 3.067551

Search

Search Cloud CMS provides full-text and structured search for all of your content. The platform uses Elastic Search under the hood to automatically create and manage search indexes for your content so that you can find anything at any time. The platform also offers "composite" search operations which let you layer searches on top of structured queries and traversals around node objects. Cloud CMS automatically indexes all of your content, including both it's JSON structure and any binary attachm

Score: 3.0479581

API / Data Types / Domain User

Domain User Type domainuser Datastore Type domain Supports authorities, permissions, transfer Configuration Domain Users maintain a configuration that you can adjust or consult as you create, update and query for them. The following table presents you the configuration properties. Property Type Default Read-Only Description name text The name (i.e. the user id or account name) for the principal. This can be any text that you like. However, it must be unique across all users in the domain. For ex

Score: 3.0479581

Security / Teams

Teams In addition to fine-grained, object-level security, Cloud CMS also offers simplified team-based security. Team-based security works provides an easier, sweeping way to manage security. By adding someone to a team, you describe broad stroke authorities that apply to all objects within a container. For example, you might create a "consumers" team for a Project. The "consumers" team grants the Consumer role. Once someone is added to that team, they will receive the Consumer role for everythin

Score: 3.0237763

Team-based security

In addition to fine-grained, object-level security, Cloud CMS also offers simplified team-based security. Team-based security works provides an easier, sweeping way to manage security. By adding someone to a team, you describe broad stroke authorities that apply to all objects within a container. For example, you might create a "consumers" team for a Project. The "consumers" team grants the Consumer role. Once someone is added to that team, they will receive the Consumer role for everything in a

Score: 3.0237763