Found 227 results for "access-policies conditions path"
The search executed in 0.001862364 seconds. That's fast.
![]() |
Gitana / 3.2 / Guide / Guide / Conditions / OrOr The or condition tests whether at least one of multiple sub-conditions are true. This joins the sub-conditions together in a logical OR. JSON Schema { "title": "Or", "properties": { "conditions": { "type": "array", "items": { "type": "object", "properties": { "type": { "type": "string" }, "config": { "type": "object
Score: 2.8387134
|
![]() |
Gitana / 4.0 / Data Engine / Behaviors / Conditions / OrOr The or condition tests whether at least one of multiple sub-conditions are true. This joins the sub-conditions together in a logical OR. JSON Schema { "title": "Or", "properties": { "conditions": { "type": "array", "items": { "type": "object", "properties": { "type": { "type": "string" }, "config": { "type": "object
Score: 2.8387134
|
![]() |
Gitana / 3.2 / Guide / Guide / Access Policies / Conditions / FeatureFeature 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 / FeatureFeature 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 / AndAnd 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 / AndAnd 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-subcontextrule-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-subcontextrule-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 / 3.2 / Guide / Guide / Access Policies / Samples / Editor of all Content in SpanishEditor 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 SpanishEditor 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 / SecuritySecurity Cloud CMS lets you define enterprise-grade access control policies across all of your content to ensure and assert that the right content is being accessed by the right people at all times. To achieve this, Cloud CMS offers a security engine that incorporates multiple levels of access provisioning. These include: A Role-based, multi-level Authorization engine that asserts Permissions on every API, service and DAO method invocation. Fine-grained, object-level access control lists for spe
Score: 2.4618807
|
![]() |
Gitana / 4.0 / Data Engine / Security / OverviewSecurity Cloud CMS lets you define enterprise-grade access control policies across all of your content to ensure and assert that the right content is being accessed by the right people at all times. To achieve this, Cloud CMS offers a security engine that incorporates multiple levels of access provisioning. These include: A Role-based, multi-level Authorization engine that asserts Permissions on every API, service and DAO method invocation. Fine-grained, object-level access control lists for spe
Score: 2.4618807
|
![]() |
Gitana / 3.2 / Guide / Guide / Access Policies / Conditions / ReferenceReference 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 / ReferenceReference 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 / Behaviors / Overview_page Actions Conditions Policies Rules
Score: 2.3496003
|
![]() |
Gitana / 3.2 / Guide / Guide / Access Policies / Conditions / NotNot This section describes features that are coming in 4.0 The not condition lets you perform a logical NOT operation against a sub-condition. Configuration { "type": "not", "config": { "condition": { ... } } } Sample #1 This policy document allows a principal to edit any content that is not in Spanish { "title": "My Sample Policy", "statements": [{ "action": "grant", "roles": ["consumer"], "conditions": [{ "typ
Score: 2.1543536
|
![]() |
Gitana / 4.0 / Data Engine / Security / Access Policies / Conditions / NotNot This section describes features that are coming in 4.0 The not condition lets you perform a logical NOT operation against a sub-condition. Configuration { "type": "not", "config": { "condition": { ... } } } Sample #1 This policy document allows a principal to edit any content that is not in Spanish { "title": "My Sample Policy", "statements": [{ "action": "grant", "roles": ["consumer"], "conditions": [{ "typ
Score: 2.1543536
|
![]() |
Gitana / 3.2 / Guide / Guide / Overview_page Access Policies Actions Antivirus Scanning API API Keys Applications Application Server Attachments Auditing Authentication Binary Files Branches Bulk Import Command Line Conditions Content Modeling Cookbooks Deployment Docker Features Find Forms General GraphQL Integrations Multifactor Authentication Modules Narration Optical Character Recognition Platform Policies Projects Publishing Query Recognition Releases Reports Rules Scripting Search Security Single Sign On (SSO) Supported Stacks
Score: 2.117941
|
![]() |
How to Retrieve content by their document library pathYou can retrieve content by their document library path using the CMS API using the Node API. For example, you can paginate through the children of a node using this call: http://api.cloudcms.com/docs#!/node/get_repositories_repositoryId_branches_branchId_nodes_nodeId_children GET /repositories/{repositoryId}/branches/{branchId}/nodes/{nodeId}/children?path={path} In this case, you would set "nodeId" to the value "root" to indicate the root node. And then use "path" to describe the offset. If yo
Score: 2.0954423
|
![]() |
Gitana / 3.2 / Guide / Guide / Access Policies / Conditions / TypeType This section describes features that are coming in 4.0 The type condition allows you to constrain a policy statement so that it applies to entities of a specific type. This condition supports regular expressions, allowing you to focus in on a single ID or wildcard expressions within an ID. Configuration { "type": "type", "config": { "type": "{type name}" } } Samples This policy document grants the Consumer role to all Projects. { "title": "My Sample Policy", "st
Score: 2.0943418
|
![]() |
Gitana / 4.0 / Data Engine / Security / Access Policies / Conditions / TypeType This section describes features that are coming in 4.0 The type condition allows you to constrain a policy statement so that it applies to entities of a specific type. This condition supports regular expressions, allowing you to focus in on a single ID or wildcard expressions within an ID. Configuration { "type": "type", "config": { "type": "{type name}" } } Samples This policy document grants the Consumer role to all Projects. { "title": "My Sample Policy", "st
Score: 2.0943418
|
![]() |
Gitana / 3.2 / Guide / Guide / Access Policies / Conditions / IDID This section describes features that are coming in 4.0 The id condition allows you to constrain a policy statement so that it applies to entities that match a given ID. This condition supports regular expressions, allowing you to focus in on a single ID or wildcard expressions within an ID. Configuration { "type": "id", "config": { "id": "{value regex}" } } Samples This policy document grants the Consumer role to a specific piece of content with the ID 46ba5e0d79b83aac97e
Score: 2.0827384
|
![]() |
Gitana / 4.0 / Data Engine / Security / Access Policies / Conditions / IDID This section describes features that are coming in 4.0 The id condition allows you to constrain a policy statement so that it applies to entities that match a given ID. This condition supports regular expressions, allowing you to focus in on a single ID or wildcard expressions within an ID. Configuration { "type": "id", "config": { "id": "{value regex}" } } Samples This policy document grants the Consumer role to a specific piece of content with the ID 46ba5e0d79b83aac97e
Score: 2.0827384
|
![]() |
Gitana / 3.2 / Guide / Guide / Access Policies / Conditions / PropertyProperty This section describes features that are coming in 4.0 The property condition allows you to constrain a policy statement so that it applies to entities where a specific property matches a value. This condition supports regular expressions, allowing you to focus in on a single ID or wildcard expressions within an ID. Configuration { "type": "property", "config": { "property": "{property name}", "value": "{property value or regex}" } } Samples This policy docu
Score: 2.0599127
|
![]() |
Gitana / 4.0 / Data Engine / Security / Access Policies / Conditions / PropertyProperty This section describes features that are coming in 4.0 The property condition allows you to constrain a policy statement so that it applies to entities where a specific property matches a value. This condition supports regular expressions, allowing you to focus in on a single ID or wildcard expressions within an ID. Configuration { "type": "property", "config": { "property": "{property name}", "value": "{property value or regex}" } } Samples This policy docu
Score: 2.0599127
|