Found 133 results for "access-policies conditions changeset"

The search executed in 0.002100464 seconds. That's fast.

Introduction to Changeset Versioning

Cloud CMS provides you with content repositories that are powered by a “changeset” versioning model. This a powerful versioning model that you won’t find in most conventional CMS products. It’s one of the reasons why Cloud CMS is such a great platform for collaboration! Document-level Versioning A lot of legacy CMS products feature document-level versioning. With document-level versioning, when you make a change to a document, the system simply increments a version counter. You end up with multi

Score: 2.7935834

Gitana / 3.2 / Guide / Guide / Access Policies / Conditions / Path

Path This section describes features that are coming in 4.0 The path condition allows you to constrain a policy statement so that it applies to content nodes that exist at a matching path. This condition supports regular expressions, allowing you to focus in on a single path, sub paths or arbitrary matching path structures. Configuration { "type": "path", "config": { "path": "{value regex}" } } Samples This policy document grants the Consumer role to all content in the path

Score: 2.7757804

Gitana / 4.0 / Data Engine / Security / Access Policies / Conditions / Path

Path This section describes features that are coming in 4.0 The path condition allows you to constrain a policy statement so that it applies to content nodes that exist at a matching path. This condition supports regular expressions, allowing you to focus in on a single path, sub paths or arbitrary matching path structures. Configuration { "type": "path", "config": { "path": "{value regex}" } } Samples This policy document grants the Consumer role to all content in the path

Score: 2.7757804

Gitana / 3.2 / Guide / Guide / Access Policies / Conditions / Or

Or This section describes features that are coming in 4.0 The or condition lets you perform a logical OR operation across multiple sub-conditions. Configuration { "type": "or", "config": { "conditions": [ ... subconditions ] } } Sample #1 This policy document allows a principal to read content from the /products and /images folders. { "title": "My Sample Policy", "statements": [{ "action": "grant", "roles": ["consumer"], "c

Score: 2.7730556

Gitana / 4.0 / Data Engine / Security / Access Policies / Conditions / Or

Or This section describes features that are coming in 4.0 The or condition lets you perform a logical OR operation across multiple sub-conditions. Configuration { "type": "or", "config": { "conditions": [ ... subconditions ] } } Sample #1 This policy document allows a principal to read content from the /products and /images folders. { "title": "My Sample Policy", "statements": [{ "action": "grant", "roles": ["consumer"], "c

Score: 2.7730556

Gitana / 3.2 / Guide / Guide / Access Policies / Conditions / Feature

Feature This section describes features that are coming in 4.0 The feature condition allows you to constrain a policy statement so that it applies to content nodes that have a particular feature. Configuration { "type": "feature", "config": { "qname": "{qname regex}" } } Samples This policy grants the Consumer role to all content with feature f:thumbnailable: { "title": "My Sample Policy", "statements": [{ "action": "grant", "roles": ["consumer"],

Score: 2.7553475

Gitana / 4.0 / Data Engine / Security / Access Policies / Conditions / Feature

Feature This section describes features that are coming in 4.0 The feature condition allows you to constrain a policy statement so that it applies to content nodes that have a particular feature. Configuration { "type": "feature", "config": { "qname": "{qname regex}" } } Samples This policy grants the Consumer role to all content with feature f:thumbnailable: { "title": "My Sample Policy", "statements": [{ "action": "grant", "roles": ["consumer"],

Score: 2.7553475

Gitana / 3.2 / Guide / Guide / Conditions / And

And The and condition tests whether one or more sub-conditions are all true. This joins the sub-conditions together in a logical AND. JSON Schema { "title": "And", "properties": { "conditions": { "type": "array", "items": { "type": "object", "properties": { "type": { "type": "string" }, "config": { "type": "object"

Score: 2.7527494

Gitana / 4.0 / Data Engine / Behaviors / Conditions / And

And The and condition tests whether one or more sub-conditions are all true. This joins the sub-conditions together in a logical AND. JSON Schema { "title": "And", "properties": { "conditions": { "type": "array", "items": { "type": "object", "properties": { "type": { "type": "string" }, "config": { "type": "object"

Score: 2.7527494

Gitana / 3.2 / Guide / Guide / UI Developers Guide / Contexts / rule-subcontext

rule-subcontext [ { "config": { "rule-subcontext": { "items": [ { "key": "rule", "header": true, "title": "Rule", "items": [ { "key": "properties", "title": "Properties", "uri": "{projectUri}/rules/{documentId}", "order": 1000 }, { "key": "binding", "title": "Policies",

Score: 2.7088206

Gitana / 4.0 / Developers / User Interface Customization / Contexts / rule-subcontext

rule-subcontext [ { "config": { "rule-subcontext": { "items": [ { "key": "rule", "header": true, "title": "Rule", "items": [ { "key": "properties", "title": "Properties", "uri": "{projectUri}/rules/{documentId}", "order": 1000 }, { "key": "binding", "title": "Policies",

Score: 2.7088206

Gitana / 4.0 / Data Engine / Security / Access Policies

Access Policies Access Control Policy documents are JSON documents that live at the Platform level. They provide a recipe that describes the access control that should be granted to any policy holder that is assigned the policy. Users may be assigned the policy directly, via a group or via a Team. Policy Document The Access Control Policy document provides a series of Statements that declare truths about what authority rights the policy holder should have over resources in the system. Each State

Score: 2.6787567

Gitana / 3.2 / Guide / Guide / Access Policies

Access Policies This section describes features that are coming in 4.0 Access Control Policy documents are JSON documents that live at the Platform level. They provide a recipe that describes the access control that should be granted to any policy holder that is assigned the policy. Users may be assigned the policy directly, via a group or via a Team. Policy Document The Access Control Policy document provides a series of Statements that declare truths about what authority rights the policy hold

Score: 2.6512766

Enterprise Access Policies in Gitana 4.0 (Part 1)

In this article, we'll take a look at Access Policies -- a powerful, new feature in Gitana 4.0 that allows organizations to set up and guarantee compliance with complex, enterprise-wide security requirements. Access Policies build upon the existing access control facilities provided which include per-object ACLs and broader, team-based ACLs. They extend those capabilities by allowing administrators to express access rights in a broad sweeping and prescriptive manner -- one that allows for custom

Score: 2.6113505

Gitana / 3.2 / Guide / Guide / Access Policies / Samples / Editor of all Content in Spanish

Editor of all Content in Spanish This section describes features that are coming in 4.0 JSON { "title": "Editor of all Content in Spanish", "statements": [{ "action": "grant", "roles": ["editor"], "conditions": [{ "conditions": [{ "type": "locale", "config": { "locale": "es" } }] }] }] }

Score: 2.588883

Gitana / 4.0 / Data Engine / Security / Access Policies / Samples / Editor of all Content in Spanish

Editor of all Content in Spanish This section describes features that are coming in 4.0 JSON { "title": "Editor of all Content in Spanish", "statements": [{ "action": "grant", "roles": ["editor"], "conditions": [{ "conditions": [{ "type": "locale", "config": { "locale": "es" } }] }] }] }

Score: 2.588883

Gitana / 3.2 / Guide / Guide / Access Policies / Samples / Manager of all Content in a Folder

Manager of all Content in a Folder This section describes features that are coming in 4.0 JSON { "title": "Manager of all Content in a Folder", "statements": [{ "action": "grant", "roles": ["manager"], "conditions": [{ "conditions": [{ "type": "path", "config": { "path": "^/my/folder/.*" } }] }] }] }

Score: 2.579999

Gitana / 4.0 / Data Engine / Security / Access Policies / Samples / Manager of all Content in a Folder

Manager of all Content in a Folder This section describes features that are coming in 4.0 JSON { "title": "Manager of all Content in a Folder", "statements": [{ "action": "grant", "roles": ["manager"], "conditions": [{ "conditions": [{ "type": "path", "config": { "path": "^/my/folder/.*" } }] }] }] }

Score: 2.579999

Gitana / 3.2 / Guide / Guide / Features / Copied From

Copied From QName: f:copied-from Indicates that a specific revision of a node received its content from a copy operation. This feature can be used to identify points in the node history where a copy operation occurred from a different node (even a node from a different branch or repository entirely) into the current node. The Copied From feature tracks a single property called sourceRef which is a node reference to the node on the source branch that was the source for the copy operation. The Cop

Score: 2.5014033

Gitana / 4.0 / Data Engine / Aspects / Copied From

Copied From QName: f:copied-from Indicates that a specific revision of a node received its content from a copy operation. This feature can be used to identify points in the node history where a copy operation occurred from a different node (even a node from a different branch or repository entirely) into the current node. The Copied From feature tracks a single property called sourceRef which is a node reference to the node on the source branch that was the source for the copy operation. The Cop

Score: 2.5014033

Enterprise Access Policies in Gitana 4.0 (Part 2)

In this article, we'll continue our series on Access Policies within Gitana. We'll take a few interesting and more complex examples of how Access Policies may be used to guarantee compliance witih enterprise security requirements. In the previous article, we left off looking at how you can grant access to content using Access Policies that are defined at either a Platform or Project-level. Platform-scoped policies can be written once and applied across all of your Projects. In this way, you can

Score: 2.4965005

Gitana / 3.2 / Guide / Guide / Access Policies / Conditions / Reference

Reference This section describes features that are coming in 4.0 The reference condition allows you to constrain a policy statement so that it applies to entities that match a given Reference. This condition supports regular expressions, allowing you to focus in on a single Reference or wildcard expressions within an Reference. In Cloud CMS, a Reference is a string that uniquely locates an item within the system. It takes on a structure that looks like one of the following: {type}://{platformId}

Score: 2.449901

Gitana / 4.0 / Data Engine / Security / Access Policies / Conditions / Reference

Reference This section describes features that are coming in 4.0 The reference condition allows you to constrain a policy statement so that it applies to entities that match a given Reference. This condition supports regular expressions, allowing you to focus in on a single Reference or wildcard expressions within an Reference. In Cloud CMS, a Reference is a string that uniquely locates an item within the system. It takes on a structure that looks like one of the following: {type}://{platformId}

Score: 2.449901

Gitana / 3.2 / Guide / Guide / Docker / Maintenance / Repository Compression

Repository Compression Cloud CMS content is stored within a Repository. A Repository differs from other types of data stores in that it provides Copy-On-Write mechanics using Changeset-driven versioning. Every time you create, update or delete content within a repository, those adjustments are written onto a new Changeset. Changesets are layered automatically and provide a stack of differences that, over time, allow you to scroll back to any moment in time to see a perfect capture of every modif

Score: 2.4400046

Gitana / 4.0 / Self Managed / Maintenance / Repository Compression

Repository Compression Cloud CMS content is stored within a Repository. A Repository differs from other types of data stores in that it provides Copy-On-Write mechanics using Changeset-driven versioning. Every time you create, update or delete content within a repository, those adjustments are written onto a new Changeset. Changesets are layered automatically and provide a stack of differences that, over time, allow you to scroll back to any moment in time to see a perfect capture of every modif

Score: 2.4400046