Found 717 results for "api node"
The search executed in 0.002379889 seconds. That's fast.
Recommended Cloud CMS architectureIn general, we recommend a three-tier architecture (browser -> app server -> API) for any applications you build. This would be our recommendation whether you're using Cloud CMS or anyone else. There are a few good reasons: The browser is an insecure runtime. Exposing any API keys within the browser is a very big security hole. Even exposing credentials within the browser (such as within a cookie) for the sake of working around this is also not recommended since hackers can siphon off the creden
Score: 1.2718183
|
|
Gitana / 3.2 / Guide / Guide / Docker / Container Services / KubernetesKubernetes Kubernetes, also known as K8s, is an open-source system for automating the deployment, scaling, and management of containerized applications. Kubernetes is open-source and adaptable to a number of cloud providers including Amazon, Google, Azure and others. It allows you to express your infrastructure configuration in such a way as to take advantage of on-premises and a diversity of hybrid and public cloud infrastructures. For information on Kubernetes, please visit https://kubernetes.
Score: 1.2710632
|
|
Gitana / 3.2 / Guide / Guide / Application Server / Authentication / Providers / GitHubGitHub Cloud CMS provides integrated authentication and single-sign-on (SSO) with GitHub. This page describes the authentication provider available for the Cloud CMS Application Server that enables your mobile or web applications as well as the Cloud CMS user interface or API to authenticate against GitHub. For more information on Authentication within the App Server, see App Server Authentication / SSO. GitHub API Keys You will need to configure a GitHub application and have the following infor
Score: 1.2669564
|
|
Gitana / 3.2 / Guide / Guide / Application Server / Authentication / Providers / GoogleGoogle Cloud CMS provides integrated authentication and single-sign-on (SSO) with Google. This page describes the authentication provider available for the Cloud CMS Application Server that enables your mobile or web applications as well as the Cloud CMS user interface or API to authenticate against Google. For more information on Authentication within the App Server, see App Server Authentication / SSO. Google API Keys You will need to configure a Google application and have the following infor
Score: 1.2669564
|
|
Gitana / 3.2 / Guide / Guide / Application Server / Authentication / Providers / TwitterTwitter Cloud CMS provides integrated authentication and single-sign-on (SSO) with Twitter. This page describes the authentication provider available for the Cloud CMS Application Server that enables your mobile or web applications as well as the Cloud CMS user interface or API to authenticate against Twitter. For more information on Authentication within the App Server, see App Server Authentication / SSO. Twitter API Keys You will need to configure a Twitter application and have the following
Score: 1.2669564
|
|
Gitana / 4.0 / Developers / Application Server / Authentication / Providers / GitHubGitHub Cloud CMS provides integrated authentication and single-sign-on (SSO) with GitHub. This page describes the authentication provider available for the Cloud CMS Application Server that enables your mobile or web applications as well as the Cloud CMS user interface or API to authenticate against GitHub. For more information on Authentication within the App Server, see App Server Authentication / SSO. GitHub API Keys You will need to configure a GitHub application and have the following infor
Score: 1.2669564
|
|
Gitana / 4.0 / Developers / Application Server / Authentication / Providers / GoogleGoogle Cloud CMS provides integrated authentication and single-sign-on (SSO) with Google. This page describes the authentication provider available for the Cloud CMS Application Server that enables your mobile or web applications as well as the Cloud CMS user interface or API to authenticate against Google. For more information on Authentication within the App Server, see App Server Authentication / SSO. Google API Keys You will need to configure a Google application and have the following infor
Score: 1.2669564
|
|
Gitana / 4.0 / Developers / Application Server / Authentication / Providers / TwitterTwitter Cloud CMS provides integrated authentication and single-sign-on (SSO) with Twitter. This page describes the authentication provider available for the Cloud CMS Application Server that enables your mobile or web applications as well as the Cloud CMS user interface or API to authenticate against Twitter. For more information on Authentication within the App Server, see App Server Authentication / SSO. Twitter API Keys You will need to configure a Twitter application and have the following
Score: 1.2669564
|
|
Gitana / 4.0 / Self Managed / Configuration / Encrypting PropertiesEncrypting Properties Cloud CMS lets you encrypt properties within your API configuration files to protect sensitive passwords, secrets and credentials. This encryption utilizes a public and private key. The private key is supplied to the Cloud CMS API server and the public key is provided to developers to encrypt sensitive data. To help you do this, Cloud CMS provides a command line tool. gitana-tools-encryptor.jar The gitana-tools-encryptor.jar works with Java 8 and gives you commands that you
Score: 1.2642648
|
|
Gitana / 3.2 / Guide / Guide / Binary Files / File System Binary StorageFile System Binary Storage Cloud CMS supports store binary files to a direct file system volume or mount by 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 written down to the file system for persistence. When users seek to download those binary files, they are streamed back from disk. Depending on how you elect to configure your binary storage providers, Clou
Score: 1.2606854
|
|
Gitana / 4.0 / Data Engine / Platform / Binary Files / File System Binary StorageFile System Binary Storage Cloud CMS supports store binary files to a direct file system volume or mount by 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 written down to the file system for persistence. When users seek to download those binary files, they are streamed back from disk. Depending on how you elect to configure your binary storage providers, Clou
Score: 1.2606854
|
|
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.2591274
|
|
Enterprise Data Engine - GitanaEnterprise Data Engine - 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
Score: 1.2555593
|
|
Gitana / 3.2 / Guide / Guide / API / Rate LimitingRate Limiting Important This section only applies to Cloud CMS Hosted Subscriptions Your Cloud CMS subscription may be configured to limit the number of concurrent API calls you are allowed to make per band. This is known as rate-limiting. When the number of concurrent API calls exceeds your tenant's configured rate limit for a given band, you will experience rate limiting. Generally, this consists of receiving an HTTP 429 response code and response headers that describe the rate limiting. The a
Score: 1.2339183
|
|
Gitana / 3.2 / Guide / Guide / Application Server / Installation / Docker InstallationDocker Installation The Cloud CMS Application Server is additionally provided as a Docker image. With Docker, you can launch this image within its own container running on Linux, Mac OS or Windows. The container can be managed, brought online and shutdown at any time. Docker To get started, you will need to familiarize yourself with Docker. Install Docker onto your operating system and become familiar with the command line tools. Git You will also need to be familiar with Git. The source for the
Score: 1.2339183
|
|
Gitana / 4.0 / Developers / Application Server / Installation / Docker InstallationDocker Installation The Cloud CMS Application Server is additionally provided as a Docker image. With Docker, you can launch this image within its own container running on Linux, Mac OS or Windows. The container can be managed, brought online and shutdown at any time. Docker To get started, you will need to familiarize yourself with Docker. Install Docker onto your operating system and become familiar with the command line tools. Git You will also need to be familiar with Git. The source for the
Score: 1.2339183
|
|
Gitana / 3.2 / Guide / Guide / Docker / Maintenance / Health Check / Load BalancersHealth Check / Load Balancers In a production configuration of Cloud CMS, you will want to have a load balancer (LB) in front of both your API and UI clusters. You should have one load balancer for the API cluster and one load balancer for the UI cluster. Each load balancer is responsible for receiving requests from the outside world and efficiently distributing those requests to the N servers that make up each cluster. Load balancers use a number of strategies to try to determine which servers
Score: 1.2253621
|
|
Gitana / 4.0 / Self Managed / Maintenance / Health Check / Load BalancersHealth Check / Load Balancers In a production configuration of Cloud CMS, you will want to have a load balancer (LB) in front of both your API and UI clusters. You should have one load balancer for the API cluster and one load balancer for the UI cluster. Each load balancer is responsible for receiving requests from the outside world and efficiently distributing those requests to the N servers that make up each cluster. Load balancers use a number of strategies to try to determine which servers
Score: 1.2253621
|
|
Gitana / 4.0 / Home / OverviewDocumentation Welcome to the Gitana Documentation Center. Gitana is a secure, enterprise-scale content platform that provides the fastest way to easily and continuously release approved, fresh content changes to your customer-facing APIs, web sites, applications and AI models. It provides everything that you need to power engaging digital experiences. It makes it easy for your business to create, manage and publish amazing content to your customers in real-time. Getting Started If you're new to
Score: 1.2217883
|
|
Gitana / 3.2 / Guide / Guide / Overview_page Access Policies Actions Antivirus Scanning API API Keys Applications Application Server Attachments Auditing Authentication Binary Files Branches Bulk Import Command Line Conditions Content Modeling Cookbooks Deployment Docker Features Find Forms General GraphQL Integrations Multifactor Authentication Modules Narration Optical Character Recognition Platform Policies Projects Publishing Query Recognition Releases Reports Rules Scripting Search Security Single Sign On (SSO) Supported Stacks
Score: 1.2195901
|
|
Gitana / 3.2 / Guide / Guide / Policies / Property PoliciesProperty Policies Property policies provide places where you can hook in behaviors that trigger when a property is created, updated or deleted. They allow you to get very granular about when you custom code is invoked - such as only when a specific property in your content is affected. The following property policies are available: Policy QName Description p:beforeCreateProperty Raised before a property on a node is created p:afterCreateProperty Raised after a property on a node is created p:bef
Score: 1.2189496
|
|
Gitana / 4.0 / Data Engine / Behaviors / Policies / Property PoliciesProperty Policies Property policies provide places where you can hook in behaviors that trigger when a property is created, updated or deleted. They allow you to get very granular about when you custom code is invoked - such as only when a specific property in your content is affected. The following property policies are available: Policy QName Description p:beforeCreateProperty Raised before a property on a node is created p:afterCreateProperty Raised after a property on a node is created p:bef
Score: 1.2189496
|
|
Gitana / 3.2 / Guide / Guide / Integrations / Azure / TranslateAzure Translate The Microsoft Translator API is a neural machine translation service that developers can easily integrate into their applications websites, tools, or any solution requiring multi-language support such as website localization, e-commerce, customer support, messaging applications, internal communication, and more. Cloud CMS provides a Microsoft Translator API Provider that works with Azure Translate to automatically create and update I18N translations as changes are made to content
Score: 1.2155348
|
|
Gitana / 4.0 / Data Engine / Integrations / Azure / TranslateAzure Translate The Microsoft Translator API is a neural machine translation service that developers can easily integrate into their applications websites, tools, or any solution requiring multi-language support such as website localization, e-commerce, customer support, messaging applications, internal communication, and more. Cloud CMS provides a Microsoft Translator API Provider that works with Azure Translate to automatically create and update I18N translations as changes are made to content
Score: 1.2155348
|
|
Gitana / 3.2 / Guide / Guide / Docker / Security Notices / CVE-2022-22965CVE-2022-22965 Cloud CMS API Container Cloud CMS API docker containers version 3.2.75 and prior ship with a version of the Spring Framework that has been identified to contain a vulnerability. This vulnerability is identified as CVE-2022-22965 and the vulnerability report can be found here: https://tanzu.vmware.com/security/cve-2022-22965 We have assessed this vulnerability and recommend that our customers either upgrade to Cloud CMS 3.2.76 or apply the workaround recommended in this docoument.
Score: 1.2145059
|