Found 146 results for "scripting principal"
The search executed in 0.001819641 seconds. That's fast.
Gitana / 3.2 / Guide / Guide / CookbooksCookbooks We've put together the following Cook Books to help you get started coding using the Cloud CMS drivers. Content Modeling Cookbook C# Cookbook Go Cookbook Java Cookbook JavaScript (Legacy) Cookbook JavaScript 2.0 Cookbook Node.js Cookbook PHP Cookbook Python Cookbook REST API Cookbook Ruby Cookbook Scripting Cookbook
Score: 3.191884
|
|
Gitana / 4.0 / Developers / Cookbooks / OverviewCookbooks We've put together the following Cook Books to help you get started coding using the Cloud CMS drivers. Content Modeling Cookbook C# Cookbook Go Cookbook Java Cookbook JavaScript (Legacy) Cookbook JavaScript 2.0 Cookbook Node.js Cookbook PHP Cookbook Python Cookbook REST API Cookbook Ruby Cookbook Scripting Cookbook
Score: 3.191884
|
|
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: 3.0661325
|
|
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: 2.6616638
|
|
Gitana / 3.2 / Guide / Guide / Command Line / Transfer CommandsTransfer Commands The Cloud CMS command-line tool provides developers with a command-line driven mechanism that allows them to: export content from Cloud CMS as an Archive import content into new Cloud CMS environments using that Archive Archives consist of ZIP files that store a full capture of the exported content. Archives may consist of an entire snapshot export or they may be partial (spanning date ranges or changeset ranges in the case of Repositories). The Cloud CMS Transfer Services make
Score: 2.652534
|
|
Gitana / 3.2 / Guide / Guide / Command Line / Modules CommandsModules Commands The Cloud CMS command-line tool provides developers with a command-line driven mechanism that allows them to: register and unregister user interface modules deploy and undeploy user interface modules User Interface Modules are deployed from public Git repositories (such as GitHub) and consist of AMD JavaScript modules. These modules contain JavaScript, HTML, CSS, a JSON configuration file any additional client-side assets that may be used (such as images). For more information a
Score: 2.5862293
|
|
Gitana / 3.2 / Guide / Guide / User Interface / Security / Create a new RoleCreate a new Role The Roles for a Project can be managed on the Roles page. For reference, here are the default Roles available: Let's take a look at the list of the default roles: Roles Description Collaborator “CONNECT”, “READ”, “CREATE_SUBOBJECTS”, “UPDATE”, “DELETE” Connector “CONNECT” Consumer "CONNECT”, “READ” Contributor “CONNECT”, “READ”, “CREATE_SUBOBJECTS” Editor “CONNECT”, “READ”, “UPDATE”, “DELETE” Impersonator “IMPERSONATE” Manager “CONNECT”, “READ”, “CREATE_SUBOBJECTS”, “UPDATE”, “
Score: 2.5372581
|
|
Gitana / 3.2 / Guide / Guide / User Interface / Security / Create a new TeamCreate a new Team The Teams for a Project can be managed on the Teams page: First Step is to create the Team - To Create a new Team click 'Create Team' Second Step is to add Roles to the team Select Roles - Click '+Grant Role' - Select the Roles you want for the Team. Note: if you do not see the Role(s) needed for your Team you will need to create the Roles. Let's take a look at the list of the default roles: Roles Description Collaborator “CONNECT”, “READ”, “CREATE_SUBOBJECTS”, “UPDATE”, “DELET
Score: 2.5372581
|
|
Gitana / 4.0 / User Interface / Security / Create a new RoleCreate a new Role The Roles for a Project can be managed on the Roles page. For reference, here are the default Roles available: Let's take a look at the list of the default roles: Roles Description Collaborator “CONNECT”, “READ”, “CREATE_SUBOBJECTS”, “UPDATE”, “DELETE” Connector “CONNECT” Consumer "CONNECT”, “READ” Contributor “CONNECT”, “READ”, “CREATE_SUBOBJECTS” Editor “CONNECT”, “READ”, “UPDATE”, “DELETE” Impersonator “IMPERSONATE” Manager “CONNECT”, “READ”, “CREATE_SUBOBJECTS”, “UPDATE”, “
Score: 2.5372581
|
|
Gitana / 4.0 / User Interface / Security / Create a new TeamCreate a new Team The Teams for a Project can be managed on the Teams page: First Step is to create the Team - To Create a new Team click 'Create Team' Second Step is to add Roles to the team Select Roles - Click '+Grant Role' - Select the Roles you want for the Team. Note: if you do not see the Role(s) needed for your Team you will need to create the Roles. Let's take a look at the list of the default roles: Roles Description Collaborator “CONNECT”, “READ”, “CREATE_SUBOBJECTS”, “UPDATE”, “DELET
Score: 2.5372581
|
|
Gitana / 3.2 / Guide / Guide / Security / PermissionsPermissions Every data store and object in Cloud CMS maintains access control lists so that you can finely describe the rights of any principal in the system against it. This lets you finely tune the rights of individual users against data stores and objects down to a single permission. This access control is authority-based which means that it's applied by granting authorities (or roles) that a principal has over an object. Let's buckle down on the terminology for a moment: A Permissioned entit
Score: 2.503887
|
|
Gitana / 4.0 / Data Engine / Security / PermissionsPermissions Every data store and object in Cloud CMS maintains access control lists so that you can finely describe the rights of any principal in the system against it. This lets you finely tune the rights of individual users against data stores and objects down to a single permission. This access control is authority-based which means that it's applied by granting authorities (or roles) that a principal has over an object. Let's buckle down on the terminology for a moment: A Permissioned entit
Score: 2.503887
|
|
Gitana / 4.0 / Developers / API / Resources / principal / Creates a principal within a domainCreates a principal within a domain The incoming JSON payload should contain properties for the newly created principal If a 'password' property is provided, an identity will be created in the domain's default directory
Score: 2.2486649
|
|
Gitana / 4.0 / Developers / API / Resources / principal / Updates a principal in a domainUpdates a principal in a domain The incoming JSON payload should contain the full set of properties to be updated onto the principal. A special 'password' property can be supplied to change a domain user's password.
Score: 2.2467313
|
|
Gitana / 3.2 / Guide / Guide / API / System MetadataSystem Metadata Cloud CMS automatically tracks system metadata for all of the objects that you create within it. System metadata consists of non-data values that describe things like who created an object and when it was modified. System Metadata This system metadata is tracked under the special _system key at the root of your objects. This system metadata is read-only in so far as it is tracked by Cloud CMS automatically. It is available for any object returned by any of the Cloud CMS APIs by s
Score: 2.1531894
|
|
Gitana / 4.0 / Data Engine / API / System MetadataSystem Metadata Cloud CMS automatically tracks system metadata for all of the objects that you create within it. System metadata consists of non-data values that describe things like who created an object and when it was modified. System Metadata This system metadata is tracked under the special _system key at the root of your objects. This system metadata is read-only in so far as it is tracked by Cloud CMS automatically. It is available for any object returned by any of the Cloud CMS APIs by s
Score: 2.1531894
|
|
Gitana / 3.2 / Guide / Guide / Text Analysis / Text Analysis Providers / AWS ComprehendAWS Comprehend Handles the Text Analysis processing of elements in a textual payload using the Amazon Web Service Comprehend Service. The AWS Comprehend Service is described by: accessKey secretKey region Where the accessKey and secretKey are used to identify an IAM principal who has sufficient authority to invoke AWS Comprehend within the given region. In addition, the IAM principal needs sufficient authorities to read, write and delete an S3 object from the given S3 bucket (identified by buck
Score: 2.1435134
|
|
Gitana / 4.0 / Data Engine / Services / Text Analysis / Text Analysis Providers / AWS ComprehendAWS Comprehend Handles the Text Analysis processing of elements in a textual payload using the Amazon Web Service Comprehend Service. The AWS Comprehend Service is described by: accessKey secretKey region Where the accessKey and secretKey are used to identify an IAM principal who has sufficient authority to invoke AWS Comprehend within the given region. In addition, the IAM principal needs sufficient authorities to read, write and delete an S3 object from the given S3 bucket (identified by buck
Score: 2.1435134
|
|
Gitana / 3.2 / Guide / Guide / Security / AuthoritiesAuthorities Every data store and object in Cloud CMS maintains access control lists so that you can finely describe the rights of any principal in the system against it. This lets you finely tune the rights of individual users against data stores and objects down to a single permission. This access control is authority-based which means that it's applied by granting authorities (or roles) that a principal has over an object. Let's buckle down on the terminology for a moment: A Permissioned entit
Score: 2.137435
|
|
Gitana / 4.0 / Data Engine / Security / AuthoritiesAuthorities Every data store and object in Cloud CMS maintains access control lists so that you can finely describe the rights of any principal in the system against it. This lets you finely tune the rights of individual users against data stores and objects down to a single permission. This access control is authority-based which means that it's applied by granting authorities (or roles) that a principal has over an object. Let's buckle down on the terminology for a moment: A Permissioned entit
Score: 2.137435
|
|
Gitana / 3.2 / Guide / Guide / Narration / Narration Providers / AWS PollyAWS Polly Handles the generation of a Narration audio file for textual content using the AWS Polly Narration Service. The AWS Polly Service is described by: accessKey secretKey region bucketName Where the accessKey and secretKey are used to identify an IAM principal who has sufficient authority to invoke AWS Polly within the given region. In addition, the IAM principal needs sufficient authorities to read, write and delete an S3 object from the given S3 bucket (identified by bucketName) within
Score: 2.1295373
|
|
Gitana / 3.2 / Guide / Guide / Optical Character Recognition / OCR Providers / AWS TextractAWS Textract Handles the Optical Character Recognition detection and analysis of characters in a binary payload using the Amazon Web Services Textract Service. The AWS Textract Service is described by: accessKey secretKey region bucketName Where the accessKey and secretKey are used to identify an IAM principal who has sufficient authority to invoke AWS Textract within the given region. In addition, the IAM principal needs sufficient authorities to read, write and delete an S3 object from the gi
Score: 2.1295373
|
|
Gitana / 3.2 / Guide / Guide / Recognition / Recognition Providers / AWS RekognitionAWS Rekognition Handles the Image Recognition detection and analysis of elements in a binary payload using the Amazon Web Service Rekognition Service. The AWS Rekognition Service is described by: accessKey secretKey region bucketName Where the accessKey and secretKey are used to identify an IAM principal who has sufficient authority to invoke AWS Rekognition within the given region. In addition, the IAM principal needs sufficient authorities to read, write and delete an S3 object from the given
Score: 2.1295373
|
|
Gitana / 3.2 / Guide / Guide / Transcription / Transcription Providers / AWS TranscribeAWS Transcribe Handles the generation of a Transcription text file for audio content using the AWS Transcribe Service. The AWS Transcribe Service is described by: accessKey secretKey region bucketName Where the accessKey and secretKey are used to identify an IAM principal who has sufficient authority to invoke AWS Transcribe within the given region. In addition, the IAM principal needs sufficient authorities to read, write and delete an S3 object from the given S3 bucket (identified by bucketNa
Score: 2.1295373
|
|
Gitana / 4.0 / Data Engine / Services / Narration / Narration Providers / AWS PollyAWS Polly Handles the generation of a Narration audio file for textual content using the AWS Polly Narration Service. The AWS Polly Service is described by: accessKey secretKey region bucketName Where the accessKey and secretKey are used to identify an IAM principal who has sufficient authority to invoke AWS Polly within the given region. In addition, the IAM principal needs sufficient authorities to read, write and delete an S3 object from the given S3 bucket (identified by bucketName) within
Score: 2.1295373
|