Found 77 results for "conditions property-changed"
The search executed in 0.001485193 seconds. That's fast.
![]() |
Gitana / 3.2 / Guide / Guide / Access Policies / Samples / Manager of all Content in a FolderManager 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 FolderManager 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
|
![]() |
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 / 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 / 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
|
![]() |
The Gitana Blog - Page 1 - GitanaThe Gitana Blog - Page 1 - Gitana Status Releases Registry Blog Cloud CMS Platform Content Management Create, Approve and Publish quality content to production on-time. Easy editorial and workflow tools let your best work reach your customers. Enterprise Data Engine Manage, collaborate, search and distribute your highly-structured data across branches, versions and workflow-driven lifecycle. Automate Automate your content creation and approval flows while taking advantage of AI services to enhan
Score: 2.342874
|
![]() |
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
|