Found 734 results for "gitana 4.0 engine security access-policies conditions not"
The search executed in 0.002919346 seconds. That's fast.
![]() |
Gitana 3.2 / Guide / Guide / Multifactor AuthenticationEnhance user security with Cloud CMS's Multifactor Authentication, adding an extra layer of protection to login credentials.
Score: 2.5419624
|
![]() |
Gitana 4.0 / Content Engine / Multifactor AuthenticationEnhance security with Cloud CMS Multifactor Authentication (MFA), requiring a verification code for superior protection against credential theft.
Score: 2.5419624
|
![]() |
Gitana 3.2 / Guide / Guide / Integrations / DUOEnhance security on Cloud CMS with Duo's real-time Multi-Factor Authentication, ensuring safer user logins and comprehensive content protection.
Score: 2.5377862
|
![]() |
Gitana 4.0 / Content Engine / Integrations / DUOIntegrate Duo Security with Cloud CMS for enhanced Multi-Factor Authentication, adding an extra layer of security to your content platform.
Score: 2.5377862
|
![]() |
Gitana 4.0 / Reference / Types / Access PolicyExplore our Access Policy guide to learn about creating, updating, and managing policies within the Gitana platform, complete with examples and schema details.
Score: 2.510779
|
![]() |
Gitana 4.0 / Self Managed / KubernetesDiscover our upcoming 4.0 Kubernetes configuration files or contact support@gitana.io for immediate access and assistance.
Score: 2.5079913
|
![]() |
Security: Grade ACloud CMS comes in two flavors - on-premise and hosted. For our hosted customers, we host 100% of Cloud CMS and take care of all of the data backup, migrations, security, load balancing and… well, everything! It’s the whole kit and kaboodle. It’s all of the DevOps and stuff solved for you. One of the fun aspects of this is keeping up with security requirements around SSL and HTTP Transport. Cloud CMS customers automatically gain the advantage of SSL for all of their communication with the Cloud
Score: 2.5055773
|
![]() |
Limiting Folder Access to Specific UsersWhen you create a Project in Cloud CMS, the Project is automatically configured with a Project Users team that grants the Consumer role to any project members. As a result, any members of the Project will have the ability to see all content within the Project. For many, this works just fine. However, there may be cases where you want to limit certain Folders to only be accessible by specific Users. Let's walk through some steps on how to do this. Change the Project Users team security policy Fir
Score: 2.4812555
|
![]() |
Gitana 4.0 / Content Engine / Access Policies / Conditions / ReferenceLearn how to use reference conditions in Cloud CMS to assign policies with regular expressions, focusing on specific or wildcarded entity references.
Score: 2.4772635
|
![]() |
Gitana 4.0 / Content Engine / Access Policies / Conditions / LocaleOptimize your policy conditions with locale-based constraints using regex for precise content node management.
Score: 2.4704256
|
![]() |
Recommended Cloud CMS architectureIn general, we recommend a three-tier architecture (browser -> app server -> API) for any applications you build. This would be our recommendation whether you're using Cloud CMS or anyone else. There are a few good reasons: The browser is an insecure runtime. Exposing any API keys within the browser is a very big security hole. Even exposing credentials within the browser (such as within a cookie) for the sake of working around this is also not recommended since hackers can siphon off the creden
Score: 2.4702039
|
![]() |
Team-based securityIn addition to fine-grained, object-level security, Cloud CMS also offers simplified team-based security. Team-based security works provides an easier, sweeping way to manage security. By adding someone to a team, you describe broad stroke authorities that apply to all objects within a container. For example, you might create a "consumers" team for a Project. The "consumers" team grants the Consumer role. Once someone is added to that team, they will receive the Consumer role for everything in a
Score: 2.4619749
|
![]() |
Gitana 3.2 / Guide / Guide / Security / TeamsManage security easily with Cloud CMS's team-based model, granting broad authority to team members across projects, while supporting fine-grained controls.
Score: 2.4318213
|
![]() |
Gitana 4.0 / Content Engine / TeamsManage security easily with Cloud CMS's team-based model, granting broad authority to team members across projects, while supporting fine-grained controls.
Score: 2.4318213
|
![]() |
Definitions for Date formatOur definitions are based on JSON schema and, as such, the default is to use strings for dates. The date controls in our forms engine let you customize the format string so that you can store ISO 8601 or other formats (perhaps simplified formats) as per your preference. The advantage here is simplicity with these controls and compatibility with JSON schema. The disadvantage is that MongoDB provides a lot of very powerful capabilities for range query and sorting that do not play as nicely with th
Score: 2.4143589
|
![]() |
Gitana 3.2 / Guide / Guide / UI Developers Guide / EvaluatorsLearn how evaluators define conditions for runtime configurations, impacting observed data and user permissions, with a wide variety of types available.
Score: 2.383983
|
![]() |
Gitana 4.0 / Developers / User Interface Customization / EvaluatorsDiscover how evaluators help define conditions for configuration inclusion based on runtime aspects like observables, permissions, and current user authority.
Score: 2.383983
|
![]() |
Is there a programmatic way to add more content to workflows?There is a programmatic way to add more content to workflows once they're in-flight. However, once the workflow is in-flight, the workflow process instance isn't the correct place to add things. Instead, you'd want to add new content to a workflow task. Essentially, a workflow is made up of a series of tasks. When the workflow transitions from one node to another in the workflow model, it instantiates a new task and the task holds the state (and references to documents) for that phase of the wor
Score: 2.373233
|
![]() |
Gitana 3.2 / Guide / Guide / Single Sign On (SSO) / OktaConfigure Cloud CMS SSO with Okta using SAML 2.0 for seamless enterprise authentication and efficient identity management.
Score: 2.371688
|
![]() |
Gitana 4.0 / Developers / Frameworks / AngularJSConnect Gitana content to your Angular app easily. Follow step-by-step instructions to set up API Keys and kickstart your project with sample code.
Score: 2.3671818
|
![]() |
Gitana 3.2 / Guide / Guide / UI Developers Guide / ModulesLearn how to create, customize, and manage CloudCMS modules to enhance your editorial team's workflow with tailored UI elements and permissions control.
Score: 2.3502402
|
![]() |
Gitana 4.0 / Content Engine / BehaviorsExplore detailed Gitana engine documentation on actions, conditions, policies, and rules to enhance your development workflow.
Score: 2.3470888
|
![]() |
Gitana 4.0 / Getting Started / Working with Content / FormsCreate and customize dynamic web forms with Cloud CMS’s intuitive engine, leveraging Alpaca.js for seamless integration with JSON Schema.
Score: 2.3439023
|
![]() |
Gitana 3.2 / Guide / Guide / Features / ExtractableOptimize metadata extraction with Cloud CMS. Automatically extract properties from attachments to enhance your document's JSON data.
Score: 2.3343256
|
![]() |
Gitana 4.0 / Content Engine / Aspects / ExtractableOptimize metadata extraction with Cloud CMS. Automatically extract properties from attachments to enhance your document's JSON data.
Score: 2.3343256
|