Found 1173 results for "gitana 4.0 engine security access-policies conditions and"

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

How we use Docker at Cloud CMS

At Cloud CMS, we use Docker to provision our cloud infrastructure servers on top of Amazon Web Services. Our stack consists of five different clusters: Cloud CMS API Cloud CMS UI Cloud CMS App Server for Dynamic Hosting Elastic Search MongoDB With the exception of MongoDB, all of these clusters are allocated using elastic load balancing and are architected in such a way that we can spin up new servers and tear down old ones with elastic demand. That is to say, they are fully elastic in design. T

Score: 0.34534556

Cloud CMS Architecture

Cloud CMS has two clusters that we run for customers who host apps with us. One cluster is for the "app server" tier (*.cloudcms.net) and the other is the "API" tier (api.cloudcms.com). The app server cluster consists of Node.js servers, and the API is a Java-backend that is stateless and implements the full REST API: As such, the API doesn't manage connections directly. Any invocation to it is a one-shot where each request contains everything needed to assert the user's identity and proceed wit

Score: 0.34534067

Gitana 3.2 / Guide / Guide / Integrations / Okta

Integrate Okta with Cloud CMS for secure identity management and SSO support using SAML 2.0 and JWT for seamless authentication.

Score: 0.34521458

Gitana 4.0 / Content Engine / Integrations / Okta

Secure user authentication and identity management with Okta's cloud software, integrating seamlessly with Cloud CMS using SAML 2.0 or JWT for SSO support.

Score: 0.34521458

Building Applications with Ratchet JS MVC

Over the past few days, I’ve had a chance to delve back into ratchet.js which is a JavaScript MVC framework that I had a hand in building in 2010. By this point, there are a lot of JavaScript MVC frameworks that you can utilize. However, at the time we built it, we were very inspired by sammy.js, backbone.js and knockout.js. A few points on these libraries: I particularly liked sammy.js for its simplicity. The developers of that library do a great job minimizing the work and also utilized an int

Score: 0.3449813

Gitana 3.2 / Guide / Guide / Integrations / Slack

Integrate Slack with Cloud CMS to receive real-time content updates. Learn to set up bots and send Slack messages efficiently.

Score: 0.34492472

Gitana 3.2 / Guide / Guide / User Interface / Projects / Copy a Project

Easily duplicate your projects in our platform with step-by-step guidance for seamless content and user membership replication.

Score: 0.34492472

Gitana 4.0 / Content Engine / Integrations / Slack

Integrate Slack with Cloud CMS for instant messaging and updates. Set up a Slack bot easily to receive real-time notifications.

Score: 0.34492472

Gitana 4.0 / User Interface / Projects / Copy a Project

Learn how to easily duplicate projects in your platform using the Copy Project Wizard. Perfect for managing content efficiently.

Score: 0.34492472

How does multi-tenancy work?

How does multi-tenancy work? ie I want to have multiple companies with sub-groups of users in each company - to follow, how would we customize the interface for each company? There are two good ways to achieve multi-tenancy with Cloud CMS. - One is to use multiple "projects" - i.e. one per customer. Each project has it's own domain of users and groups, as well as it's own content definitions, instances and ACLs. As such, you can use each project to store the content on a per-client basis. You ca

Score: 0.34472507

How does Cloud CMS compare to DIY (do-it-yourself)?

Not sure whether to build or buy? Review these points to help guide your selection. Why DIY: exact fit with your technology stack use existing in-house skills and resources build only the features you need able to add new features as required use existing developers for support cost / budget - internal no need for external services to deliver and support product can be a ‘skunk works’ project Why not DIY: Risk (more complex than it looks) time/effort/cost are all easy to under-estimate CMS requi

Score: 0.3447076

Comparison: Cloud CMS vs DIY

Not sure whether to build or buy? Review these points to help guide your selection. Why DIY: exact fit with your technology stack use existing in-house skills and resources build only the features you need able to add new features as required use existing developers for support cost / budget - internal no need for external services to deliver and support product can be a ‘skunk works’ project Why not DIY: Risk (more complex than it looks) time/effort/cost are all easy to under-estimate CMS requi

Score: 0.3447076

Gitana 3.2 / Guide / Guide / Integrations / Amazon Web Services / Amazon Translate

Amazon Translate offers fast, accurate neural machine translation for websites and apps. Learn how Cloud CMS integrates for seamless I18N updates.

Score: 0.34443438

Gitana 4.0 / Content Engine / Integrations / Amazon Web Services / Amazon Translate

Discover seamless language translation with Amazon Translate, a neural machine service providing accurate, swift, and economical translations for global content.

Score: 0.34443438

Gitana 3.2 / Guide / Guide / Branches / Custom Indexes

Optimize your data retrieval with custom indexes in Cloud CMS, enabling faster queries and improved performance for large datasets.

Score: 0.34442368

Gitana 4.0 / Content Engine / Branches / Custom Indexes

Optimize Cloud CMS performance with custom branch-level indexes for faster data queries and efficient app performance.

Score: 0.34442368

Gitana 3.2 / Guide / Guide / Integrations / ActiveMQ

Optimize your backend applications with ActiveMQ, a high-performance message broker, integrated with Cloud CMS for seamless API notifications.

Score: 0.344384

Gitana 3.2 / Guide / Guide / Publishing / Example Publishing Setup

Learn how to configure a complete publishing setup, from project creation to publishing and unpublishing in this detailed guide.

Score: 0.344384

Gitana 4.0 / Content Engine / Integrations / ActiveMQ

Optimize your Cloud CMS integration using Apache ActiveMQ for seamless API event handling and message queuing. Enhance scalability and performance.

Score: 0.344384

Gitana 4.0 / Forms / API / Connectors

Enhance Alpaca forms with custom and default connectors to seamlessly load data, schemas, and options from remote sources like Cloud CMS.

Score: 0.344384

Gitana 3.2 / Guide / Guide / Getting Started / Multiple Projects

Collaborate seamlessly on diverse projects with customizable roles for team members. Create, review, and publish content efficiently in a secure platform.

Score: 0.34429395

Gitana 4.0 / Getting Started / Using your Data Platform / Projects

Collaborate on versatile projects with customized roles for efficient content creation, approval, and publication across platforms. Create your ideal team space!

Score: 0.34429395

Gitana 3.2 / Guide / Guide / User Interface / Dashboard

Customize your platform dashboards with ease. Change layouts, add or remove dashlets, manage configurations, and lock settings effortlessly.

Score: 0.34354204

Gitana 4.0 / User Interface / User Interface / Dashboard

Customize your dashboard in Platform and Project with ease. Change layout, add or remove dashlets, configure, and lock with flexible options.

Score: 0.34354204

Oauth 2.0 tokens

Each response from Cloud CMS provides two tokens: an access token and a refresh token. The access token is the one that you need to attach to every API call. It gets passed through the Authorization header as "bearer " and Cloud CMS uses this to identify who the authenticated user is (and thus, what resources they have access to and so forth). By default, the access token has a lifespan of 24 hours. After that period of time, it is no longer valid and any requests will come back wit

Score: 0.34350353