Found 144 results for "recognition providers aws-rekognition"
The search executed in 0.00150341 seconds. That's fast.
Gitana / 3.2 / Guide / Guide / Applications / Public Services / Setting up your Email ProviderSetting up your Email Provider The public application services often need to send emails as part of their respective flows. To do this, a public email provider must be configured for the application. This is email provider that the public services will use when dispatching emails as part of a public flow. On this page, we cover a few convenience methods that are available to test your email provider as well as send emails straight away. This page assumes that you are already familiar with email
Score: 1.5336703
|
|
Gitana / 4.0 / Data Engine / Platform / Applications / Public Services / Setting up your Email ProviderSetting up your Email Provider The public application services often need to send emails as part of their respective flows. To do this, a public email provider must be configured for the application. This is email provider that the public services will use when dispatching emails as part of a public flow. On this page, we cover a few convenience methods that are available to test your email provider as well as send emails straight away. This page assumes that you are already familiar with email
Score: 1.5336703
|
|
Gitana / 3.2 / Guide / Guide / Application Server / Services / CacheCache The Cache Service is responsible for providing an application server cache that all processes, whether local or distributed, have access to for non-transactional caching. Objects stored in the cache are eventually available to other members of the cluster (if there are any), no matter whether running on the same server or on other servers in the cluster. Modes The Cloud CMS Application Server can run in one of three modes: single node cluster multiple nodes (on a single process) sticky-clu
Score: 1.4482814
|
|
Gitana / 4.0 / Developers / Application Server / Services / CacheCache The Cache Service is responsible for providing an application server cache that all processes, whether local or distributed, have access to for non-transactional caching. Objects stored in the cache are eventually available to other members of the cluster (if there are any), no matter whether running on the same server or on other servers in the cluster. Modes The Cloud CMS Application Server can run in one of three modes: single node cluster multiple nodes (on a single process) sticky-clu
Score: 1.4482814
|
|
Gitana / 3.2 / Guide / Guide / Binary FilesBinary Files Cloud CMS lets you upload any kind of desktop file. The system will automatically detect the type of content that you upload and will inspect and work with the content to provide the following services: Automatic antivirus scanning to detect malicious files Extraction of metadata properties from the payload body and headers Conversion of content type to thumbnails (using image transformation) Detection and extraction of text for full-text search Execution of custom rules to further
Score: 1.3982043
|
|
Gitana / 4.0 / Data Engine / Platform / Binary FilesBinary Files Cloud CMS lets you upload any kind of desktop file. The system will automatically detect the type of content that you upload and will inspect and work with the content to provide the following services: Automatic antivirus scanning to detect malicious files Extraction of metadata properties from the payload body and headers Conversion of content type to thumbnails (using image transformation) Detection and extraction of text for full-text search Execution of custom rules to further
Score: 1.3982043
|
|
Gitana / 3.2 / Guide / Guide / Binary Files / GridFS Binary StorageGridFS Binary Storage Cloud CMS supports MongoDB GridFS by allowing it to serve as a backend provider for the storage of binary files within Cloud CMS. When files are uploaded to Cloud CMS, they are parsed and worked with and then eventually sent over to Amazon S3 for persistence. When users seek to download those binary files, they are streamed back from S3. Depending on how you elect to configure your binary storage providers, Cloud CMS may employ an TTL cache in between to avoid going back to
Score: 1.3668411
|
|
Gitana / 4.0 / Data Engine / Platform / Binary Files / GridFS Binary StorageGridFS Binary Storage Cloud CMS supports MongoDB GridFS by allowing it to serve as a backend provider for the storage of binary files within Cloud CMS. When files are uploaded to Cloud CMS, they are parsed and worked with and then eventually sent over to Amazon S3 for persistence. When users seek to download those binary files, they are streamed back from S3. Depending on how you elect to configure your binary storage providers, Cloud CMS may employ an TTL cache in between to avoid going back to
Score: 1.3668411
|
|
Gitana / 3.2 / Guide / Guide / API / Data Types / Billing Provider ConfigurationBilling Provider Configuration 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}} If this sounds familiar, it's because it's exactly what Cloud CMS uses to supports its own subscription plans for Cloud CMS custom
Score: 1.3077673
|
|
Gitana / 3.2 / Guide / Guide / 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: 1.3077673
|
|
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: 1.3077673
|
|
Gitana / 4.0 / Data Engine / API / Data Types / Billing Provider ConfigurationBilling Provider Configuration 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}} If this sounds familiar, it's because it's exactly what Cloud CMS uses to supports its own subscription plans for Cloud CMS custom
Score: 1.3077673
|
|
Gitana / 3.2 / Guide / Guide / Single Sign On (SSO) / PingPing This page provides information on how to configure Cloud CMS Single Sign On (SSO) for Ping Identity's PingOne Single Sign-on with SAML 2.0. Cloud CMS provides Single Sign On (SSO) Enterprise support for a variety of Identity Providers using SAML 2.0 and/or JWT. For more information, see Cloud CMS Single Sign On (SSO). You can learn more about Ping Identity and PingOne here: https://www.pingidentity.com/en/cloud/pingone-enterprise.html Set up PingOne In this section, we'll set up Single Sig
Score: 1.240999
|
|
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: 1.240999
|
|
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: 1.240999
|
|
Gitana / 4.0 / Data Engine / Authentication / Single Sign On (SSO) / PingPing This page provides information on how to configure Cloud CMS Single Sign On (SSO) for Ping Identity's PingOne Single Sign-on with SAML 2.0. Cloud CMS provides Single Sign On (SSO) Enterprise support for a variety of Identity Providers using SAML 2.0 and/or JWT. For more information, see Cloud CMS Single Sign On (SSO). You can learn more about Ping Identity and PingOne here: https://www.pingidentity.com/en/cloud/pingone-enterprise.html Set up PingOne In this section, we'll set up Single Sig
Score: 1.240999
|
|
Migrating Binary files to S3By default, on-premise installations of Cloud CMS are configured with a GridFS (`gridfs`) Binary Storage Provider. This allows Cloud CMS to read and write binary files (such as attachments) to GridFS. At some point, as your installation grows, you may want change this. Suppose you wanted to move your binary files into S3 and use S3 as a Binary Storage Provider for Cloud CMS. To do so, we recommend the following steps: 1. Make a backup of your Cloud CMS database. 2. Create an S3 bucket and IAM us
Score: 1.240999
|
|
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: 1.2040477
|
|
Gitana / 3.2 / Guide / Guide / Single Sign On (SSO) / OktaOkta This page provides information on how to configure Cloud CMS Single Sign On (SSO) for Okta and SAML 2.0. Cloud CMS provides Single Sign On (SSO) Enterprise support for a variety of Identity Providers using SAML 2.0 and/or JWT. For more information, see Cloud CMS Single Sign On (SSO). You can learn more about Okta here: https://www.okta.com Set up Okta In this section, we'll set up Single Sign On with Okta. Log into the Okta Administration Console Login at https://{your-okta-domain}.okta.co
Score: 1.1692331
|
|
Gitana / 4.0 / Data Engine / Authentication / Single Sign On (SSO) / OktaOkta This page provides information on how to configure Cloud CMS Single Sign On (SSO) for Okta and SAML 2.0. Cloud CMS provides Single Sign On (SSO) Enterprise support for a variety of Identity Providers using SAML 2.0 and/or JWT. For more information, see Cloud CMS Single Sign On (SSO). You can learn more about Okta here: https://www.okta.com Set up Okta In this section, we'll set up Single Sign On with Okta. Log into the Okta Administration Console Login at https://{your-okta-domain}.okta.co
Score: 1.1692331
|
|
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: 0.9253473
|
|
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: 0.9253473
|
|
Security Policy - GitanaSecurity 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 cu
Score: 0.92068696
|
|
Gitana / 3.2 / Guide / Guide / Applications / Public Services / Forgot Username FlowForgot Username Flow Registered users for your application may forget their username and lose the ability to log in to your app. Cloud CMS provides a "forgot username" flow that you can use to provide a way for end users to securely retrieve their username using their registered email address. On this page, we cover a public convenience method that applications can use to easily provide this functionality without having to through the most robust Cloud CMS object-level APIs. If you're interested
Score: 0.8680439
|
|
Gitana / 4.0 / Developers / 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: 0.8323107
|