Found 63 results for "login"
The search executed in 9.59229E-4 seconds. That's fast.
![]() |
Gitana / 4.0 / Developers / Application Server / Authentication / Providers / CustomCustom This page provides some guidance on how to define your own custom Authentication Provider class for use within the Application Server. Note: If you're looking information on how to easily integrate a third-party Authentication Provider into the Application Server, we recommend first taking a look at the Local Provider as it can be configured to work with third-party endpoints pretty easily. Implementation Class We recommend extending the AbstractProvider class. The basic skeleton of the c
Score: 7.0128326
|
![]() |
Gitana / 3.2 / Guide / Guide / Docker / Kits / MongoDB Replica SetMongoDB Replica Set The MongoDB Replica Set kit defines an environment with a 3 node MongoDB replica set and two Cloud CMS environments running against it The configuration files for this kit can be found in the Gitana SDK Running Start the mongo servers first and then initialize the cluster: docker login --username {docker-username} --password '{docker-password}' docker-compose up -d mongodb1 mongodb2 mongodb3 Initialize the replic set. only have to do this once since the mongo servers persist
Score: 6.9653554
|
![]() |
New reporting optionsWe’ve added some expanded reports lately: for both Workflow, as well as Logging. Since it’s introduction, workflow remains a key component of our platform. The process to define and execute various business processes in Cloud CMS is well documented. Now, you can track and analyze each step involved to streamline operations even further: Review any historical sequence of events, or those currently in-flight, to find patterns / trends / bottlenecks needing attention. Especially where system log de
Score: 6.4004326
|
![]() |
Gitana / 3.2 / Guide / Guide / Application Server / AuthenticationAuthentication The Authentication Service provides a full authentication framework for stateless and session-based applications. It authenticates requests against back end providers and offers interpretation and parsing of request scope information to provide Single-Sign-On (SSO). Authenticated requests will have user accounts created and synchronized within Cloud CMS either automatically or as part of a registration form process. Authenticated users have Cloud CMS connectivity state managed for
Score: 6.397527
|
![]() |
Gitana / 4.0 / Developers / Application Server / AuthenticationAuthentication The Authentication Service provides a full authentication framework for stateless and session-based applications. It authenticates requests against back end providers and offers interpretation and parsing of request scope information to provide Single-Sign-On (SSO). Authenticated requests will have user accounts created and synchronized within Cloud CMS either automatically or as part of a registration form process. Authenticated users have Cloud CMS connectivity state managed for
Score: 6.397527
|
![]() |
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.30964
|
![]() |
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.30964
|
![]() |
Gitana / 4.0 / Self Managed / Configuration / UI ServerUI Server The Cloud CMS UI Server is a Node.js application that provides the editorial experience for Cloud CMS. It communicates with the Cloud CMS API via HTTP/HTTPS API calls and is built to be very extensible. Developers and system integrators can extend the Cloud CMS UI through the deployment of UI modules. Environment File (.env) The Cloud CMS UI is primarily configured via a series of environment variables. These environment variables are detected by the Node.js application at startup and
Score: 6.2652035
|
![]() |
Single Sign On (SSO)Cloud CMS introduces a Single Sign-On service that will make it easy for the users to connect using their already existing business accounts. Cloud CMS supports 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 Federation Services (ADFS), JBoss Keycloak etc. Using SAML 2.0 and JWT, Cloud CMS can be easily integrated with your corporate security infrastructure.
Score: 6.1803474
|
![]() |
Gitana / 3.2 / Guide / Guide / Multifactor AuthenticationMultifactor Authentication Cloud CMS supports Multifactor Authentication (MFA) to provide enhanced security for your users and their account credentials. With Multifactor Authentication is enabled for a user, that user will be required to supply a verification code in addition to their username and password. The verification code is delivered to the user's phone or mobile device via SMS, a phone call or an app. The code may also be delivered via a hardware device depending on the kind of provide
Score: 5.8723745
|
![]() |
Gitana / 4.0 / Data Engine / Authentication / Multifactor AuthenticationMultifactor Authentication Cloud CMS supports Multifactor Authentication (MFA) to provide enhanced security for your users and their account credentials. With Multifactor Authentication is enabled for a user, that user will be required to supply a verification code in addition to their username and password. The verification code is delivered to the user's phone or mobile device via SMS, a phone call or an app. The code may also be delivered via a hardware device depending on the kind of provide
Score: 5.8723745
|
![]() |
Gitana / 3.2 / Guide / Guide / Docker / Configuration / UI ServerUI Server The Cloud CMS UI Server is a Node.js application that provides the editorial experience for Cloud CMS. It communicates with the Cloud CMS API via HTTP/HTTPS API calls and is built to be very extensible. Developers and system integrators can extend the Cloud CMS UI through the deployment of UI modules. Environment File (.env) The Cloud CMS UI is primarily configured via a series of environment variables. These environment variables are detected by the Node.js application at startup and
Score: 5.675708
|
![]() |
What is an Identity vs a User?The concept of an Identity and a User is distinct in Cloud CMS. They are separate things. Essentially, a User holds the name, email address and other properties about a user and an Identity holds the password. A User may optionally have an identity associated with it but this isn't required. For any users that you want to give the ability to log in, you'll need to have an identity created and associated for them. This is as easy as editing the user and setting their password. When a password is
Score: 5.471543
|
![]() |
Gitana / 3.2 / Guide / Guide / User Interface / Security / Add a User to a ProjectAdd a User to a Project Option 1: Create User in the Tenant At Platform level, select 'Member' (left nav) and '+Create User' Enter the values on the forms and 'Save'. Result: User is now created. Note: The new user will not be able to see any projects when they login the new user will be seen in the Tenant members list and will be available to be added as an 'existing user' to any project Second Step is to add the user to a Project Select Members (left Nav) -> add existing user. select the user
Score: 5.3740516
|
![]() |
Gitana / 4.0 / User Interface / Security / Add a User to a ProjectAdd a User to a Project Option 1: Create User in the Tenant At Platform level, select 'Member' (left nav) and '+Create User' Enter the values on the forms and 'Save'. Result: User is now created. Note: The new user will not be able to see any projects when they login the new user will be seen in the Tenant members list and will be available to be added as an 'existing user' to any project Second Step is to add the user to a Project Select Members (left Nav) -> add existing user. select the user
Score: 5.3740516
|
![]() |
Gitana / 3.2 / Guide / Guide / PlatformPlatform Cloud CMS provides a Platform within which you can build out one or more Projects to create, manage and deliver your content. You can create as many Projects as you wish and are also free to duplicate, back up, download or export Projects at any time. Users You can add users to your Platform at any time. When users log in, they log in to the Platform and are then able to see all of the Projects that they have access to. You may choose to invite some users to have some permissions agains
Score: 5.2799735
|
![]() |
Gitana / 4.0 / Data Engine / Platform / OverviewPlatform Cloud CMS provides a Platform within which you can build out one or more Projects to create, manage and deliver your content. You can create as many Projects as you wish and are also free to duplicate, back up, download or export Projects at any time. Users You can add users to your Platform at any time. When users log in, they log in to the Platform and are then able to see all of the Projects that they have access to. You may choose to invite some users to have some permissions agains
Score: 5.2799735
|
![]() |
Alpaca 1.0.3 Released!We’re pleased to announce the release of Alpaca Web Forms 1.0.3 for jQuery, jQuery UI and jQuery Mobile. Alpaca is an open-source project that provides an easy way to render web forms using JSON schema. It consists of a jQuery plugin and provides a nice abstraction so that you can change form layouts, validation logic and presentation with simple changes to JSON. Alpaca provides the web forms capabilities for Cloud CMS - The Cloud Content Management Platform for the Enterprise. This release incl
Score: 4.7781014
|
![]() |
Gitana / 3.2 / Guide / Guide / Application ServerApplication Server The Cloud CMS Application Server offers an easy way for customers to assemble powerful, front-end custom APIs and web sites for Cloud CMS. It is completely free and runs on top of the popular Node.js technology stack. With Cloud CMS, customers have a choice of using any front-end presentation technology they wish. In many cases, customers already have a technology investment (such as C#, PHP, Java or Ruby) and thus a preference for continuing to build on that technology stack.
Score: 4.493365
|
![]() |
Gitana / 4.0 / Developers / Application Server / OverviewApplication Server The Cloud CMS Application Server offers an easy way for customers to assemble powerful, front-end custom APIs and web sites for Cloud CMS. It is completely free and runs on top of the popular Node.js technology stack. With Cloud CMS, customers have a choice of using any front-end presentation technology they wish. In many cases, customers already have a technology investment (such as C#, PHP, Java or Ruby) and thus a preference for continuing to build on that technology stack.
Score: 4.493365
|
![]() |
Gitana / 3.2 / Guide / Guide / AuthenticationAuthentication 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: 4.398471
|
![]() |
Gitana / 4.0 / Data Engine / Authentication / OverviewAuthentication 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: 4.398471
|
![]() |
Privacy Policy - GitanaPrivacy Policy - Gitana Status Releases Registry Blog Cloud CMS Platform Content Management Create, Approve and Publish quality content to production on-time. Easy editorial and workflow tools let your best work reach your customers. Enterprise Data Engine Manage, collaborate, search and distribute your highly-structured data across branches, versions and workflow-driven lifecycle. Automate Automate your content creation and approval flows while taking advantage of AI services to enhance and cur
Score: 3.4351335
|
![]() |
Access Cloud CMS content anonymously or as a guest userThis question often comes up from folks who are building HTML applications that run in a browser. They'd like the browser to connect to Cloud CMS to download content and display it. Usually this consists of things like images but also may consist of other types of content in Cloud CMS such as raw nodes, PDF files, video assets or more. OAuth 2.0 and Access Tokens Fundamentally, everything in Cloud CMS is secured from an access perspective using OAuth 2.0. This means that an OAuth 2.0 access toke
Score: 3.2388186
|
![]() |
Users, Identities and SSO with Cloud CMSOne of the really interesting use cases for Cloud CMS is that of maintaining users across multiple domains while having those users share a common identity context. A common identity context allows an authentication session to transition seamlessly (via an authentication swap) from one user to the next. It also allows for properties (such as username, email, password or other custom user properties) to automatically synchronize across all of the user identities that are part of the context. Here
Score: 3.2388186
|