Found 427 results for "appserver authentication authenticators custom"
The search executed in 0.002578833 seconds. That's fast.
Does Cloud CMS support Single Sign On (SSO)?Yes, Cloud CMS supports SSO (Single Sign On) with a variety of authentication providers. Many of these providers are offered out-of-the-box -- including providers for Keycloak, Google, CAS and more. In addition, we allow you to implement your own SSO providers and customize the authentication handshake. To learn more about how Cloud CMS authentication providers work, check out the following documentation: https://www.cloudcms.com/documentation/appserver/services/auth.html Custom Authenticators a
Score: 8.317978
|
|
Gitana / 4.0 / Data Engine / Content Models / BehaviorsBehaviors Cloud CMS lets you wire in behaviors behind your content models so that rules automatically execute when your content is touched. Content editors work with simple forms to create content that conforms to your defined content models. When that content is created, updated or deleted, it automatically triggers policies (or events) which you use to bind in custom behaviors. In this way, the developers can wire up behaviors and the editorial team never needs to know about it. Furthermore, b
Score: 8.313317
|
|
Gitana / 3.2 / Guide / Guide / DeploymentDeployment Cloud CMS Deployment lets you publish content from a source Cloud CMS project branch to one or more destination Deployment Endpoints. These Deployment Endpoints may include Amazon S3 buckets, FTP servers, file system locations and Cloud CMS branches on the same cluster or running in a cluster located in another data center somewhere else in the world. The Deployment process can be triggered manually or automatically. It may run as part of a Publishing process for your content. It may
Score: 8.240412
|
|
Gitana / 4.0 / Data Engine / Deployment / OverviewDeployment Cloud CMS Deployment lets you publish content from a source Cloud CMS project branch to one or more destination Deployment Endpoints. These Deployment Endpoints may include Amazon S3 buckets, FTP servers, file system locations and Cloud CMS branches on the same cluster or running in a cluster located in another data center somewhere else in the world. The Deployment process can be triggered manually or automatically. It may run as part of a Publishing process for your content. It may
Score: 8.240412
|
|
Gitana / 3.2 / Guide / Guide / UI Developers GuideUI Developers Guide 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 editorial
Score: 8.222214
|
|
Gitana / 4.0 / Developers / User Interface Customization / OverviewUI Developers Guide 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 editorial
Score: 8.222214
|
|
Gitana / 3.2 / Guide / Guide / API / Data Types / Authentication GrantAuthentication Grant Type {{#dataTypeArticle objectTypeId}}{{objectTypeId}}{{/dataTypeArticle}} Datastore Type {{#dataTypeArticle datastoreTypeId}}{{datastoreTypeId}}{{/dataTypeArticle}} Supports {{#article "security/authorities"}}authorities{{/article}}, {{#article "security/permissions"}}permissions{{/article}}, {{#article "transfer"}}transfer{{/article}} Why would you want to use an Authentication Grant? Here are a few reasons: Authentication Grants provide a way for you to distribute user au
Score: 7.5386887
|
|
Gitana / 4.0 / Data Engine / API / Data Types / Authentication GrantAuthentication Grant Type {{#dataTypeArticle objectTypeId}}{{objectTypeId}}{{/dataTypeArticle}} Datastore Type {{#dataTypeArticle datastoreTypeId}}{{datastoreTypeId}}{{/dataTypeArticle}} Supports {{#article "security/authorities"}}authorities{{/article}}, {{#article "security/permissions"}}permissions{{/article}}, {{#article "transfer"}}transfer{{/article}} Why would you want to use an Authentication Grant? Here are a few reasons: Authentication Grants provide a way for you to distribute user au
Score: 7.5386887
|
|
Gitana / 3.2 / Guide / Guide / 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: 7.4945927
|
|
Gitana / 4.0 / Data Engine / Authentication / 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: 7.4945927
|
|
Gitana / 3.2 / Guide / Guide / FeaturesFeatures Features are aspect-oriented, cross-cutting concerns that can be applied to nodes. Once applied, they may introduce new behaviors and metadata to your content objects. You can use features to describe cross-cutting or aspect-oriented concerns that can be plugged onto your content nodes at any time. Features may participate in the inheritance tree of content types or they may be injected anywhere and at any point. There are a number of out-of-the-box features provided by Cloud CMS, inclu
Score: 6.7163453
|
|
Gitana / 4.0 / Data Engine / Aspects / OverviewFeatures Features are aspect-oriented, cross-cutting concerns that can be applied to nodes. Once applied, they may introduce new behaviors and metadata to your content objects. You can use features to describe cross-cutting or aspect-oriented concerns that can be plugged onto your content nodes at any time. Features may participate in the inheritance tree of content types or they may be injected anywhere and at any point. There are a number of out-of-the-box features provided by Cloud CMS, inclu
Score: 6.7163453
|
|
Gitana / 3.2 / Guide / Guide / Application Server / Authentication / Providers / LocalLocal The Local Authentication Provider enables the Cloud CMS Application Server to connect to a locally implemented identity provider. The identity provider can be implemented within your own Node.js application or as part of a separate application using a completely different technology. 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 (default values are shown): "auth": {
Score: 6.442583
|
|
Gitana / 4.0 / Developers / Application Server / Authentication / Providers / LocalLocal The Local Authentication Provider enables the Cloud CMS Application Server to connect to a locally implemented identity provider. The identity provider can be implemented within your own Node.js application or as part of a separate application using a completely different technology. 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 (default values are shown): "auth": {
Score: 6.442583
|
|
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: 5.70687
|
|
Gitana / 3.2 / Guide / Guide / Branches / Custom IndexesCustom Indexes Cloud CMS internally maintains indexes to improve the speed of your data lookups across all data store types. In most cases, there is no need to concern yourself with these as they deliver optimal performance. With respect to content repositories, however, Cloud CMS allows you to define custom database indexes on a per-branch basis. These custom indexes add to the default set that Cloud CMS automatically maintains. Each branch and/or snapshot maintains its own "tip" collection tha
Score: 5.560273
|
|
Gitana / 4.0 / Data Engine / Branches / Custom IndexesCustom Indexes Cloud CMS internally maintains indexes to improve the speed of your data lookups across all data store types. In most cases, there is no need to concern yourself with these as they deliver optimal performance. With respect to content repositories, however, Cloud CMS allows you to define custom database indexes on a per-branch basis. These custom indexes add to the default set that Cloud CMS automatically maintains. Each branch and/or snapshot maintains its own "tip" collection tha
Score: 5.560273
|
|
Gitana / 4.0 / Forms / API / Custom FieldsCustom Fields Alpaca has a pretty inclusive field library that you can use straight away. Fields are simply referenced by their type within your Alpaca forms configuration. If you don't provide specific field types to use, Alpaca guesses at sensible defaults for you. You can also create your own fields. Alpaca fields are object-oriented (essentially) so that you can extend existing fields, override methods and modify behaviors. The result is less work and a complete extensibility layer so that y
Score: 5.556784
|
|
Gitana / 3.2 / Guide / Guide / Application Server / ClusteringClustering The Cloud CMS Application Server supports running on a single Node process as well as multiple Node processes. Node processes can run on a single server instance or can be spread across multiple server instances behind a load balancer. By default, the Application Server starts up and allocates itself to a single CPU. This is known as single mode. Even if you have a server with more than one CPU on it, the Application Server will still only bind to 1 of those CPUs. When the Application
Score: 5.285649
|
|
Gitana / 3.2 / Guide / Guide / General / Custom Domain NameCustom Domain Name Cloud CMS allows you to customize the domain name for the editorial user interface. Custom domain names are supported for both SaaS and on-premise installation accounts. Tenant URL Every Cloud CMS subscriber is given a tenant domain URL that looks like this: mytenant.cloudcms.net Where mytenant is the subdomain you picked when you created your account. You're free to change this subdomain at any time (no additional steps needed). This URL serves back the editorial environment
Score: 4.8177695
|
|
Gitana / 4.0 / Data Engine / General / Custom Domain NameCustom Domain Name Cloud CMS allows you to customize the domain name for the editorial user interface. Custom domain names are supported for both SaaS and on-premise installation accounts. Tenant URL Every Cloud CMS subscriber is given a tenant domain URL that looks like this: mytenant.cloudcms.net Where mytenant is the subdomain you picked when you created your account. You're free to change this subdomain at any time (no additional steps needed). This URL serves back the editorial environment
Score: 4.8177695
|
|
Gitana / 3.2 / Guide / Guide / Application Server / Authentication / Providers / CASCAS 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: 4.7056103
|
|
Gitana / 4.0 / Developers / Application Server / Authentication / Providers / CASCAS 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: 4.7056103
|
|
Gitana / 3.2 / Guide / Guide / Multifactor Authentication / Providers / Twilio AuthyTwilio Authy Cloud CMS supports Twilio Authy for Multifactor Authentication. To configure Authy, you will need to supply the following: apiUrl apiSecret These values are available from your Authy Settings page. Service Descriptor If you're adding an Authenticator via a Service Descriptor: the Descriptor Type should be TWILIO_AUTHY. the Descriptor Configuration should look like this: { "enabled": true, "providerType": "authy", "providerConfig": { "apiKey": "MY_API_KEY",
Score: 4.637619
|
|
Gitana / 4.0 / Data Engine / Authentication / Multifactor Authentication / Providers / Twilio AuthyTwilio Authy Cloud CMS supports Twilio Authy for Multifactor Authentication. To configure Authy, you will need to supply the following: apiUrl apiSecret These values are available from your Authy Settings page. Service Descriptor If you're adding an Authenticator via a Service Descriptor: the Descriptor Type should be TWILIO_AUTHY. the Descriptor Configuration should look like this: { "enabled": true, "providerType": "authy", "providerConfig": { "apiKey": "MY_API_KEY",
Score: 4.637619
|