Configuration

Plugin Capabilities

Introduction

This document is a guide to present:

  • The plugin capabilities

  • The plugin restrictions or limitations

Tot Plugin Capabilities

Active Governance

It allows delegating the provisioning of user groups to which access permissions are subsequently assigned to data resources governed by the product being used.

YAML
totplugin:
  server:
    url: https://tot1server.anjanadata.local:15000/tot/  
  connection:
    - name: plugin1
      aris:
        - ari: "anja:totplugin:im:/azure/ad/pre/"
      technology:
        clientId: "aaaaaaa-bbbb-cccc-dddd-eeeeeeeeeeee"
        tenantId: "aaaaaaaaaaa-bbbb-cccc-dddd-eeeeeeeeeee"
        secret: "aaaaaaaabbbbbbbbcccccccceeeeeeeeddddddddd"
        scopes: "https://graph.microsoft.com/.default"
        groupPrefix: Dsa_


In addition, it is able to create data resources in the product, which are used if an entity is created in Anjana as governed in a triplet with the active governance configuration.

YAML
totplugin:
  server:
    url: https://tot1server.anjanadata.local:15000/tot/
  connection:
    - name: plugin1
      aris:
        - ari: "anja:totplugin:extract:/azure/files/pre/"
        - ari: "anja:totplugin:sample:/azure/files/pre/"
        - ari: "anja:totplugin:edit:/azure/files/pre/"
        - ari: "anja:totplugin:im:/azure/files/pre/"
          imAri: "anja:totplugin:im:/azure/ad/pre/"
      technology:
        storageAccount: totpluginazure
        key: "aaaaaaaaabbbbbbbbbbcccccccccccddddddddeeeeeeeefffffff=="
        sampleRows: 15
        pathSeparator: "/"


In the previous example, what happens in stages is:

  1. For the plugin to which identity management will be delegated, the triplet is set up the same way as in its configuration, but starting with “imAri” below the triplet that manages the permissions.

  2. The identity management plugin (source of the imAri triplet) will create a group, granting memberships to the users, and will return an identifier to the triplet “- ari: anja:totplugin:im:”

  3. The triplet that manages the permissions (- ari: anja:totplugin:im:) will grant permissions using that received identifier through the specific technology (GRANT, ACL, …)

Data Sampling

By resolving the logical connection provided by the triplet, the plugin connects to the data resource and retrieves the first X rows of its content. It is also possible to obfuscate the information of certain sample columns based on the “pi” attribute of the DATASET_FIELDS and the ofuscationString configuration.

sampleRows: 15 → Maximum number of rows we will be able to see.

ofuscationString: “***” → Text string with which the information received from the sampling will be replaced.

YAML
totplugin:
  server:
    url: https://tot1server.anjanadata.local:15000/tot/
  connection:
    - name: plugin1
      aris:
        - ari: "anja:totplugin:extract:/azure/files/pre/"
        - ari: "anja:totplugin:sample:/azure/files/pre/"
        - ari: "anja:totplugin:im:/azure/files/pre/"
          imAri: "anja:totplugin:im:/azure/ad/pre/"
      technology:
        storageAccount: totpluginazure 
        key: "aaaaaaaaabbbbbbbbbbcccccccccccddddddddeeeeeeeefffffff=="
        sampleRows: 15
        pathSeparator: "/"


Metadata Extraction

Through the resolution of the logical connection provided by the triplet, the plugin is able to connect to the data resource and return its metadata.

YAML
totplugin:
  server:
    url: https://tot1server.anjanadata.local:15000/tot/
  connection:
     - name: plugin1
      aris:
        - ari: "anja:totplugin:extract:/azure/files/pre/"
        - ari: "anja:totplugin:sample:/azure/files/pre/"
        - ari: "anja:totplugin:im:/azure/files/pre/"
          imAri: "anja:totplugin:im:/azure/ad/pre/"
      technology:
        storageAccount: totpluginazure 
        key: "aaaaaaaaabbbbbbbbbcccccccccccddddddddeeeeeeeefffffff=="
        sampleRows: 15
        pathSeparator: "/"


Object Editing

Through the resolution of the logical connection provided by the triplet, the plugin is able to connect to the data resource and generate changes to it driven by the activation/deactivation of entities in Anjana.

YAML
totplugin:
  server:
    url: https://tot1server.anjanadata.local:15000/tot/
  connection:    
    - name: plugin1
      aris:
        - ari: "anja:totplugin:extract:/azure/files/pre/"
        - ari: "anja:totplugin:sample:/azure/files/pre/"
        - ari: "anja:totplugin:edit:/azure/files/pre/"
        - ari: "anja:totplugin:im:/azure/files/pre/"
          imAri: "anja:totplugin:im:/azure/ad/pre/"
      technology:
        storageAccount: totpluginazure
        key: "aaaaaaaaabbbbbbbbbbcccccccccccddddddddeeeeeeeefffffff=="
        sampleRows: 15
        pathSeparator: "/"

Other capabilities

There are other plugin-level capabilities, such as Tag updates, that are specific to each technology

Limitations or restrictions

  • Each plugin can manage multiple connections, so that if the infrastructure needs to connect to, for example, two different SQLServer instances, a single SQLServer plugin can include both connections.

  • It is also possible to deploy more than one plugin, each with a different connection.

    • Keep in mind that this approach implies higher resource consumption in the infrastructure.

  • In any case, keep in mind that triplets cannot be shared between different plugins or between connections of the same plugin. Each triplet must be unique.