Found 91 results for "ui ui security overview"

The search executed in 0.001 seconds

User Interface

User Interface Cloud CMS provides a full user interface that your editorial team and managers use to create, manage and deliver content to the business, mobile applications and web sites. The user interface is secure, role-based and customizable, allowing your development team to cater the editorial experience to the exact needs of end users. Awareness Dashboard Create/Edit Content Embed Media In CKEditor Favorites Multilingual Image Editor Locking Menu Projects Releases Search Security Tags UI

Score: 49.84442

Modules

Modules The Cloud CMS user interface is an HTML / JavaScript application that comes pre-configured with a base application that is feature complete and out-of-the-box. It includes a ready-to-run content management and collaboration tool set for managing documents, web sites, mobile content and more. It also makes some default assumptions about page layout, placement of buttons, availability of functionality and role-based provisioning that may or may not match your desired workflow. Chances are

Score: 46.30465

User Interface / Multilingual / Customize Translations UI

Customize Translations UI Cloud CMS allows you to customize UI simply with configurations in your module. Here we will use the following example to demonstrate this feature. For multilingual documents with translations, if you go to the multilingual document's Edit Properties page, the default UI looks like this: In the above screenshot, the Edit Translations button allows you to select a translation of the multilingual document from the dropdown. It's a way to quickly edit the translated docume

Score: 40.575348

Getting Started

Getting Started Welcome to the Cloud CMS Documentation center. Cloud CMS is an API-first content management system that provides everything you need on the back end to power web sites and mobile applications. Cloud CMS makes it easy for your business users to create, manage and publish amazing content to your users! You are reading the Getting Started guide. To learn more about Cloud CMS and what it does, select from the links provided below or use the tree on the left-hand side. We offer severa

Score: 38.60617

Security

Security Cloud CMS provides two ways to describe access rights to things: Object-level / role-based authorities Team / role-based authorities With object-level / role-based authorities, you assign a principal (either a user or a group) a role against something. For example, you might give Joe the CONSUMER role against a content node. When Joe then interacts with the content node in the future, he will do so with the CONSUMER role which will allow him to "read" the node. With team / role-based au

Score: 30.064905

User Interface / UI Views

UI Views Customized changes to the user interface configuration can be introduced through the use of UI Config documents. UI Config documents are JSON documents that contain one or more configuration blocks. The UI Config configuration blocks are loaded after the standard configuration document and therefore have the opportunity to either extend or override the base configuration. UI Configs are scoped either to the platform or to the project. As such, you can use UI Config objects to customize

Score: 25.268726

User Interface / UI Templates

UI Templates On pages like "Content Types" and "Search", each list item has some detailed information displayed. You can customize the information you hope to appear via UI Templates. Create a UI Template Fill in the title and a unique key to create a new UI template. You can also write down some description for the template. Nodes with qname n:ui_template have two properties: key, which is a unique identifier of the template, and type, which is the type of targets the template is applied to. Cu

Score: 24.545475

Docker / UI Extensions

UI Extensions The Docker-based Cloud CMS UI provides additional extension patterns beyond the AMD-driven mechanism for user interface components and screens. Since Docker allows you to run on-premise, you can use these extension patterns to influence more foundational changes to the way the application works. Environment Variables When the Cloud CMS user interface starts up, it looks to environment variables to tell it whether there are any extensions available to be loaded. Extensions are store

Score: 24.322678

Application Server / Services / Overview

Overview For more information on configuration of the Cloud CMS application server, please visit Cloud CMS App Server on GitHub. { "name": "Cloud CMS Application Server", "setup": "single", // single, cluster, sticky-cluster "socketFunctions": [], "routeFunctions": [], "configureFunctions": {}, "beforeFunctions": [], "afterFunctions": [], "viewEngine": "handlebars", "storeEngines": { "app": { "type": "fs", "config": {

Score: 18.547203

Getting Started / Role-Based Editorial UI

Role-Based Editorial UI The Cloud CMS Editorial application is a responsive web site that runs on web browsers, iPad, iPhone and a myriad of other devices and form factors. It provides a place where users can work together and collaborate in meaningful ways based on the roles they have been given. As an example, when a Manager signs on to the Editorial environment, he or she will have access to many managerial functions, such as the ability to add or remove team members. Those options will appea

Score: 18.425564

Authentication

Authentication Cloud CMS supports authentication via the industry standard OAuth 2.0 protocol. OAuth 2.0 is a well-recognized standard that enables client code to connect to Cloud CMS in a secure and safe fashion. This means that authorization can be achieved in such a way that client and user credentials (secret keys) are never publicly exposed. Channel-level encryption is provided by HTTPS and HTTP POST payloads are utilized to avoid exposure of credentials via request parameters or logging fa

Score: 18.170763

User Interface / Security

Security Create a new Role Create a new Team Add a User to a Project

Score: 16.306961

Single Sign On (SSO)

Single Sign On (SSO) Cloud CMS offers Single Sign On (SSO) Enterprise support that provides ways for users to log in using their existing business accounts. It makes it possible for your users to authenticate to Cloud CMS without having to remember or type in their credentials every time. Cloud CMS offers two Enterprise SSO features - SAML 2.0 and JWT. These are two popular SSO mechanisms that work with many commercial and open-source identity providers including: Microsoft Active Directory Fede

Score: 14.947699

Multifactor Authentication / Providers / Duo Security

Duo Security Cloud CMS supports [https://duo.com/](Duo Security) for Multifactor Authentication. To configure Duo Security, you will need to supply the following: integrationKey secretKey apiHost These values are available from your Duo Security Settings page. Service Descriptor If you're adding an Authenticator via a Service Descriptor: the Descriptor Type should be DUO_AUTH. the Descriptor Configuration should look like this: { "enabled": true, "providerType": "duo", "providerConfi

Score: 13.753625

Modules / Create a Module

Create a Module Common files that each module should have: module.json (where you give the module a name) install.js uninstall.js As soon as you have these files, the rest is up to you depending on what you would like to customize in the module. Take a look at some sample modules in our SDK Actions Bindings Config Service Evaluators Plugins Templates

Score: 11.94303

Multifactor Authentication / Providers

Providers Twilio Authy Duo Security

Score: 11.42008

Advanced Content Modeling options (example)

Question. If I have the following collections: Categories Products Product_Description_Schemas Each Product is linked to a Category. Each Category is linked to a Product_Description_Schema. The outcome I want to accomplish is that the description schema for Product X I am entering, is defined by the Category it is linked to ( which in turn is defined by the Product_Description_Schema that the Category is linked to ). e.g. Product = Hilton Hotel London, Category = Hotel, Product_Description_Schem

Score: 10.434981

How does Cloud CMS compare to Contentful?

Not sure which CMS is a better fit? Review these points to help guide your selection. Criteria Cloud CMS Contentful Ease of Use Implements a role-based UI to accommodate various functions. Simple user interface for defining content types and instances. Update Strategy Documents are published individually, or as part of larger change sets. Documents are published one-by-one. Workflow Process Flexible workflow capability. Allows teams and roles to be created along with a workflow designer for defi

Score: 10.293398

User Interface / Locking

Locking Cloud CMS locking is a "data lock" approach which is a transactional lock is taken out when the write of multiple documents begins. This is a transactional lock in the sense that it blocks other write operations against those documents and fails entirely with rollback if any of the documents fail individually. We have transactional writes for multiple documents. We have a changeset-driven versioning model where each transaction writes onto it's own changeset. N number of documents may wr

Score: 10.137696

How does Cloud CMS compare to Prismic.io?

Not sure which CMS is a better fit? Review these points to help guide your selection. Criteria Cloud CMS Prismic.io Ease of Use Implements a role-based UI to accommodate various functions. Complex user interface for defining content types and instances. Item creation must occur here. See API Access. Update Strategy Documents are published individually, or as part of larger change sets. Documents are published individually, or as part of larger change sets. Workflow Process Flexible workflow capa

Score: 10.066405

Docker / Kits / OEM

OEM The OEM kit provides a way for developers, integrators, partners and those who are embedded Cloud CMS in custom solutions to build and test extensions. These extensions include UI extensions as well as API extensions in the form of Java / Spring beans. The kit consists of the following services: ui api mongodb elasticsearch These are connected like this: Running Use the following commands: docker-compose build --force-rm docker-compose up And then open a browser to: http://localhost To acces

Score: 9.154985

Docker / Kits / Quickstart

Quickstart The Quickstart kit defines the following services: ui api mongodb elasticsearch These are connected like this: Running Use the following commands: docker-compose build --force-rm docker-compose up And then open a browser to: http://localhost To access the API directly: https://localhost:8080 docker-compose.yml version: "2" services: ui: build: ./ui networks: - cloudcms depends_on: - api env_file: - ./ui/ui.env ports: - "80:80" api:

Score: 8.573893

Application Server / Authentication / Providers / SAML 2.0

SAML 2.0 The SAM Authentication Provider enables the Cloud CMS Application Server to authenticate, validate tokens and load user profile information against servers that are SAML 2.0 compatible. SAML stands for Security Assertion Markup Language. 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": "saml",

Score: 8.534326

Content Modeling / Content Model Builder / Create A New Content Type

Create A New Content Type Once you have Content Model Builder enabled, you can create a new content type from there. Click button "Create Definition" near the top left: Then give your content type a name in the pop up modal: Hit "Create" and you can find the new content model in the list. Click into it to make it more interesting with the Content Model Builder: As you can see in the above image, there are two tabs -- "UI" and "JSON". CloudCMS provides you with two ways to build a content type bu

Score: 8.389454

API Max Heap recommendation

What is the recommended Xmx value for running the API service? The 2GB setting on the On-Premise "quickstart" distribution is a default for development usage. In production, we recommend putting as much memory as you can. Essentially, the API should use as much memory as is allocated to the API docker container. We usually ask customers to consider an M class large instance type (something on the order of 7.5GB of RAM per API). The UI can use considerably less. For the UI, a 2GB allocation is fi

Score: 7.936514