Quick Processor Rights Management

Quick Processor Rights Management

To modify or create a Quick Processor, the user must have both the QuickProcessorModify right and the TopicAccessRead right.

QuickProcessorModify can be assigned for individual connections/environments. In combination with the TopicAccessRead right, which can be assigned at topic level (including wildcard and namespaces), the use of the Quick Processor can be defined for individual topics, namespaces, and environments in a fine-grained manner.

  1. {
  2.     "action": "QuickProcessorModify",
  3.     "effect": "Allow",
  4.     "resource": "*"
  5.   },
  6.   {
  7.     "action": "TopicAccessRead",
  8.     "effect": "Allow",
  9.     "resource": "*:mybusiness.myteam.*"
  10.   }

In the example above, the use of the Quick Processor is granted for all connections and environments in Kadeck, but only for streams beginning with the name mybusiness.myteam.

    • Related Articles

    • Architecture of the Quick Processor

      The following diagram illustrates the data flow of a data set. The Quick Processor is executed after the decoding process for each individual data set. A Quick Processor can be used for data transformation, but can also act as a filter with complex ...

    • ACL Rights Management

      The rights to manage or view ACLs can be configured flexibly: from basic rights that cover all ACLs to resource-specific rights with specifications on the naming scheme. The latter allows teams to independently manage resources within their working ...

    • Introduction to the Quick Processor

      The Quick Processor allows you to create filters and modify records using JavaScript. In this article, we show how to create a Quick Processor and how to access, filter, and modify records. A Quick Processor is always linked to a view. This means ...

    • Rights evaluation

      You can assign multiple roles with multiple rights to a user. The following rules apply to evaluate the rights in effect: First Rule: Specific right before less specific right. Second Rule: Allow before deny. Rule 1 example: Right1: Deny      ...

    • Manage rights and roles

      What are roles? Roles are a collection of rights that can be assigned either to groups or directly to users. The rights define the scope of functionality and data to which a user has access. Create roles and rights Go to the Roles screen in the ...