Found 310 results for "access-policies conditions feature"
The search executed in 0.001542702 seconds. That's fast.
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 / 3.2 / Guide / Guide / Access Policies / Conditions / LocaleLocale This section describes features that are coming in 4.0 The locale condition allows you to constrain a policy statement so that it applies to content nodes that have a matching locale. This condition supports regular expressions, allowing you to focus in on a single path, sub paths or arbitrary matching path structures. Configuration { "type": "locale", "config": { "locale": "{value regex}" } } Samples This policy document grants the Consumer role to all content with l
Score: 2.437786
|
|
Gitana / 4.0 / Data Engine / Security / Access Policies / Conditions / LocaleLocale This section describes features that are coming in 4.0 The locale condition allows you to constrain a policy statement so that it applies to content nodes that have a matching locale. This condition supports regular expressions, allowing you to focus in on a single path, sub paths or arbitrary matching path structures. Configuration { "type": "locale", "config": { "locale": "{value regex}" } } Samples This policy document grants the Consumer role to all content with l
Score: 2.437786
|
|
Gitana / 4.0 / Data Engine / Behaviors / Overview_page Actions Conditions Policies Rules
Score: 2.3496003
|
|
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.314907
|
|
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.314907
|
|
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
|
|
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 / 3.2 / Guide / Guide / Access Policies / Conditions / Type QNameType QName This section describes features that are coming in 4.0 The type-qname condition allows you to constrain a policy statement so that it applies to content nodes that have a matching QName. This condition supports regular expressions, allowing you to focus in on a single path, sub paths or arbitrary matching path structures. Configuration { "type": "type-qname", "config": { "qname": "{value regex}" } } Sample #1 This policy document allows a principal to read content
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 / 4.0 / Data Engine / Security / Access Policies / Conditions / Type QNameType QName This section describes features that are coming in 4.0 The type-qname condition allows you to constrain a policy statement so that it applies to content nodes that have a matching QName. This condition supports regular expressions, allowing you to focus in on a single path, sub paths or arbitrary matching path structures. Configuration { "type": "type-qname", "config": { "qname": "{value regex}" } } Sample #1 This policy document allows a principal to read content
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
|
|
Gitana / 3.2 / Guide / Guide / Access Policies / Conditions / ChangesetChangeset This section describes features that are coming in 4.0 The changeset condition allows you to constrain a policy statement so that it applies to nodes and/or associations that are written onto a matching changeset. The changeset can be matched using its ID (_doc). This condition supports regular expressions, allowing you to focus in on a single value or wildcard expressions for matches. Configuration To match a changeset by ID: { "type": "changeset", "config": { "id": "{
Score: 2.0157309
|
|
Gitana / 4.0 / Data Engine / Security / Access Policies / Conditions / ChangesetChangeset This section describes features that are coming in 4.0 The changeset condition allows you to constrain a policy statement so that it applies to nodes and/or associations that are written onto a matching changeset. The changeset can be matched using its ID (_doc). This condition supports regular expressions, allowing you to focus in on a single value or wildcard expressions for matches. Configuration To match a changeset by ID: { "type": "changeset", "config": { "id": "{
Score: 2.0157309
|
|
Gitana / 3.2 / Guide / Guide / Access Policies / Conditions / ProjectProject This section describes features that are coming in 4.0 The project condition allows you to constrain a policy statement so that it applies to entities that are contained with a project. The project can be matched using either its ID (_doc) or its title. This condition supports regular expressions, allowing you to focus in on a single value or wildcard expressions for matches. Configuration To match a project by ID: { "type": "project", "config": { "id": "{value regex}"
Score: 1.9734043
|
|
Gitana / 4.0 / Data Engine / Security / Access Policies / Conditions / ProjectProject This section describes features that are coming in 4.0 The project condition allows you to constrain a policy statement so that it applies to entities that are contained with a project. The project can be matched using either its ID (_doc) or its title. This condition supports regular expressions, allowing you to focus in on a single value or wildcard expressions for matches. Configuration To match a project by ID: { "type": "project", "config": { "id": "{value regex}"
Score: 1.9734043
|
|
Gitana / 3.2 / Guide / Guide / Access Policies / Conditions / BranchBranch This section describes features that are coming in 4.0 The branch condition allows you to constrain a policy statement so that it applies to nodes and/or associations that are on a matching branch. The branch can be matched using its ID (_doc), title or alias. This condition supports regular expressions, allowing you to focus in on a single value or wildcard expressions for matches. Configuration To match a branch by ID: { "type": "branch", "config": { "id": "{value regex}
Score: 1.9529006
|
|
Gitana / 4.0 / Data Engine / Security / Access Policies / Conditions / BranchBranch This section describes features that are coming in 4.0 The branch condition allows you to constrain a policy statement so that it applies to nodes and/or associations that are on a matching branch. The branch can be matched using its ID (_doc), title or alias. This condition supports regular expressions, allowing you to focus in on a single value or wildcard expressions for matches. Configuration To match a branch by ID: { "type": "branch", "config": { "id": "{value regex}
Score: 1.9529006
|
|
Gitana / 3.2 / Guide / Guide / Access Policies / Conditions / Data StoreData Store This section describes features that are coming in 4.0 The datastore condition allows you to constrain a policy statement so that it applies to datastores and/or objects within a datastore. The datastore can be matched using its Type, ID and/or a title. This condition supports regular expressions, allowing you to focus in on a single value or wildcard expressions for matches. Configuration To match a changeset by Type: { "type": "datastore", "config": { "typeId": "{val
Score: 1.9328187
|
|
Gitana / 4.0 / Data Engine / Security / Access Policies / Conditions / Data StoreData Store This section describes features that are coming in 4.0 The datastore condition allows you to constrain a policy statement so that it applies to datastores and/or objects within a datastore. The datastore can be matched using its Type, ID and/or a title. This condition supports regular expressions, allowing you to focus in on a single value or wildcard expressions for matches. Configuration To match a changeset by Type: { "type": "datastore", "config": { "typeId": "{val
Score: 1.9328187
|