Found 611 results for "docker configuration encrypting-properties"

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

Gitana / 4.0 / Forms / Fields / JSON Field

JSON Field The json field. Properties Title JSON Editor Description Editor for JSON objects with basic validation and formatting Field Type json Base Field Type textarea Schema Property Type Default Description allowOptionalEmpty Allows this non-required field to validate when the value is empty autocomplete string Allows you to specify the autocomplete attribute for the underlying input control whether or not field should have autocomplete enabled. data object Allows you to specify a key/value

Score: 0.75043476

Gitana / 4.0 / Forms / Fields / Phone Field

Phone Field The phone field. This editor field requires jQuery Masked Input Plugin Properties Title Phone Description Phone Field Type phone Base Field Type text Schema Property Type Default Description allowOptionalEmpty Allows this non-required field to validate when the value is empty autocomplete string Allows you to specify the autocomplete attribute for the underlying input control whether or not field should have autocomplete enabled. data object Allows you to specify a key/value map of d

Score: 0.75043476

Gitana / 4.0 / Forms / Fields / URL Field

URL Field The url field. Properties Title URL Description A color picker for selecting hexadecimal color values Field Type url Base Field Type text Schema Property Type Default Description allowOptionalEmpty Allows this non-required field to validate when the value is empty autocomplete string Allows you to specify the autocomplete attribute for the underlying input control whether or not field should have autocomplete enabled. data object Allows you to specify a key/value map of data attributes

Score: 0.75043476

Gitana / 4.0 / Forms / Fields / Zip Code Field

Zip Code Field The zipcode field. Properties Title ZIP Code Description Provides a five or nine-digital US zipcode control with validation Field Type zipcode Base Field Type text Schema Property Type Default Description allowOptionalEmpty Allows this non-required field to validate when the value is empty autocomplete string Allows you to specify the autocomplete attribute for the underlying input control whether or not field should have autocomplete enabled. data object Allows you to specify a k

Score: 0.75043476

Gitana / 3.2 / Guide / Guide / Access Policies / Conditions / Type

Type 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: 0.74923205

Gitana / 3.2 / Guide / Guide / Deployment / Deployment Handlers / Local Deployment Handler

Local Deployment Handler Handles the deployment of one or more Deployment Packages to a local Deployment Receiver. The deployment receiver must exist on the same Cloud CMS platform. It is identified by the receiverId property. The Deployment Packages will be handed to the Deployment Receiver and then processed from there. The Deployment Receiver may elect to pass those Deployment Packages down to its own configured targets or process them through additional rules priority to delivery. Configurat

Score: 0.74923205

Gitana / 3.2 / Guide / Guide / UI Developers Guide / Samples / Developer Menu Items

Developer Menu Items By default, the Developer menu group is not enabled for users with the 'collaborator' role. Here is an example of how to change the default behavior of Cloud CMS to allow Developer menu options for users with the 'collaborator' role. We could use the following configuration: { "config": { "blocks": [ { "evaluator": "context-project", "config": { "project-context": { "items": [

Score: 0.74923205

Gitana / 3.2 / Guide / Guide / Application Server / Authentication / Providers / CAS

CAS The CAS Authentication Provider enables the Cloud CMS Application Server to authenticate, validate tokens and load user profile information against servers that implement the Central Authentication Service SSO protocol (either version 2 or version 3). For more information on Authentication within the App Server, see App Server Authentication / SSO. Configuration Here are all of the properties that may be configured: "auth": { "providers": { "myProvider": { "type": "ca

Score: 0.74923205

Gitana / 4.0 / Developers / Application Server / Authentication / Providers / CAS

CAS The CAS Authentication Provider enables the Cloud CMS Application Server to authenticate, validate tokens and load user profile information against servers that implement the Central Authentication Service SSO protocol (either version 2 or version 3). For more information on Authentication within the App Server, see App Server Authentication / SSO. Configuration Here are all of the properties that may be configured: "auth": { "providers": { "myProvider": { "type": "ca

Score: 0.74923205

Gitana / 4.0 / Developers / User Interface Customization / Samples / Developer Menu Items

Developer Menu Items By default, the Developer menu group is not enabled for users with the 'collaborator' role. Here is an example of how to change the default behavior of Cloud CMS to allow Developer menu options for users with the 'collaborator' role. We could use the following configuration: { "config": { "blocks": [ { "evaluator": "context-project", "config": { "project-context": { "items": [

Score: 0.74923205

Gitana / 4.0 / Data Engine / Deployment / Deployment Handlers / Local Deployment Handler

Local Deployment Handler Handles the deployment of one or more Deployment Packages to a local Deployment Receiver. The deployment receiver must exist on the same Cloud CMS platform. It is identified by the receiverId property. The Deployment Packages will be handed to the Deployment Receiver and then processed from there. The Deployment Receiver may elect to pass those Deployment Packages down to its own configured targets or process them through additional rules priority to delivery. Configurat

Score: 0.74923205

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

Type 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: 0.74923205

Gitana / 3.2 / Guide / Guide / Deployment / Deployment Target

Deployment Target A Deployment Target contains the configuration for a Deployment Handler. It informs the handler about how to connect or what settings should be used when executing. Deployment Targets are configured for Deployment Strategies as well as for Deployment Receivers. When content is changed within Cloud CMS, a Deployment Strategy may decide to package up that modified content and deployment it to one or more Deployment Targets. Similarly, content may be deployed to a Deployment Recei

Score: 0.74508107

Gitana / 3.2 / Guide / Guide / Integrations / Keycloak

Keycloak Keycloak is an open-source Identity and Access Management product provided by JBoss/RedHat. Keycloak plays the role of an Identity Provider that speaks SAML 2.0 and/or JWT. Cloud CMS integrates via either of these mechanism and can therefore integrate to Keycloak straight away as an identity provider. Cloud CMS provides Single Sign On (SSO) Enterprise support for a variety of Identity Providers using SAML 2.0 and/or JWT. For more information, see Cloud CMS Single Sign On (SSO). To learn

Score: 0.74508107

Gitana / 3.2 / Guide / Guide / Access Policies / Conditions / ID

ID 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: 0.74508107

Gitana / 3.2 / Guide / Guide / Access Policies / Conditions / Type QName

Type 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: 0.74508107

Gitana / 3.2 / Guide / Guide / Workflow / Workflow Handlers / Remove Features

Remove Features Type: removeFeatures This handler removes features from a node that is part of the workflow's payload. This can be used to remove one or more features from your content instances as they flow through your workflow. The config for this handler is as follows: { "features": [{ "qname": "" }] } Each of the features identified by qname will be removed from the documents attached to the workflow payload. Here is an example configuration which assumes tha

Score: 0.74508107

Gitana / 4.0 / Data Engine / Deployment / Deployment Target

Deployment Target A Deployment Target contains the configuration for a Deployment Handler. It informs the handler about how to connect or what settings should be used when executing. Deployment Targets are configured for Deployment Strategies as well as for Deployment Receivers. When content is changed within Cloud CMS, a Deployment Strategy may decide to package up that modified content and deployment it to one or more Deployment Targets. Similarly, content may be deployed to a Deployment Recei

Score: 0.74508107

Gitana / 4.0 / Data Engine / Integrations / Keycloak

Keycloak Keycloak is an open-source Identity and Access Management product provided by JBoss/RedHat. Keycloak plays the role of an Identity Provider that speaks SAML 2.0 and/or JWT. Cloud CMS integrates via either of these mechanism and can therefore integrate to Keycloak straight away as an identity provider. Cloud CMS provides Single Sign On (SSO) Enterprise support for a variety of Identity Providers using SAML 2.0 and/or JWT. For more information, see Cloud CMS Single Sign On (SSO). To learn

Score: 0.74508107

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

ID 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: 0.74508107

Gitana / 4.0 / Data Engine / Security / Access Policies / Conditions / Type QName

Type 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: 0.74508107

Gitana / 4.0 / Data Engine / Workflow / Workflow Handlers / Remove Features

Remove Features Type: removeFeatures This handler removes features from a node that is part of the workflow's payload. This can be used to remove one or more features from your content instances as they flow through your workflow. The config for this handler is as follows: { "features": [{ "qname": "" }] } Each of the features identified by qname will be removed from the documents attached to the workflow payload. Here is an example configuration which assumes tha

Score: 0.74508107

Gitana / 3.2 / Guide / Guide / Features / Related

Related QName: f:related This feature is applied internally to nodes that are on the other end of a relator association to indicate that the target node is related to the source node. This feature acts as a marker to tell Cloud CMS to consider the related nodes and the relator association at persistence time so the properties can be managed more efficiently in terms of mapping values from one end of the relationship to the other. There is no need to apply or work with this feature manually. For

Score: 0.73691547

Gitana / 3.2 / Guide / Guide / Features / Word Count

Word Count QName: f:word-count Indicates that a node should track the number of words in each text property. Configuration Word Count Example Suppose we have a content type (my:article) that looks like this: { "_qname": "my:article", "_type": "d:type", "type": "object", "properties":{ "title": { "type": "string" }, "body": { "type": "string" } }, "mandatoryFeatures": { "f:word-count": {} } } Now we crea

Score: 0.73691547

Gitana / 3.2 / Guide / Guide / Access Policies / Conditions / Property

Property 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: 0.73691547