Adding a Dataiku Connection

Prerequisites

• A user with sufficient permissions is required to establish a connection with Dataiku.
• Zeenea traffic flows towards the data source must be open.

note

The Dataiku connector can be downloaded here: Zeenea Connector Downloads.

Supported Versions

The Dataiku connector is compatible with the software SaaS version.

Installing the Plugin

The Dataiku plugin can be downloaded here: Zeenea Connector Downloads.

For more information on how to install a plugin, please refer to the following article: Installing and Configuring Connectors as a Plugin.

Declaring the Connection

Creating and configuring connectors is done through a dedicated configuration file located in the /connections folder of the relevant scanner.

Read more: Managing Connections

In order to establish a connection with a Dataiku instance, specifying the following parameters in the dedicated file is required:

Parameter	Expected value
name	The name that will be displayed to catalog users for this connection.
code	The unique identifier of the connection on the Zeenea platform. Once registered on the platform, this code must not be modified or the connection will be considered as new and the old one removed from the scanner.
connector_id	The type of connector to be used for the connection. Here, the value must be dataiku and this value must not be modified.
connection.url	Dataiku instance URL (example: https://url.eu-west-3.app.dataiku.io)
connection.username	Secret token generated from the Dataiku application
tls.truststore.path	The Trust Store file path. This file must be provided in case TLS encryption is activated (protocol https) and when certificates of servers are delivered by a specific authority. It must contain the certification chain.
tls.truststore.password	Password of the trust store file
tls.truststore.type	Type of the trust store file (PKCS12 or JKS). Default value is discovered from the file extension.
proxy.scheme	Depending on the proxy, http or https
proxy.hostname	Proxy address
proxy.port	Proxy port.
proxy.username	Proxy username
proxy.password	Proxy account password

User Permissions

In order to collect metadata, the running user's permissions must allow them to access and read datasets that need cataloging.

Here, the user must have read access to Dataiku projects that need cataloging.

Data Extraction

To extract information, the connector runs the following REST requests on the API:

• GET: /public/api/projects/: To get the project list.
• GET /public/api/projects/{project name}/datasets/: To get dataset from the project.
• GET /public/api/projects/{project name}/datasets/{dataset name}/: To get metadata dataset.

Collected Metadata

Inventory

Will collect the list of datasets accessible by the user.

Dataset

• Name
• Source Description
• Technical Data:
  • Type
  • Format Type
  • Project Key
  • Updated At
  • Updated By

Field

Dataset field.

• Name
• Source Description
• Type
• Can be null: Not supported. Default value false.
• Multivalued: Not supported. Default value false.
• Primary Key: Not supported. Default value false.
• Technical Data:
  • Technical Name
  • Native type

Unique Identifier Keys

A key is associated with each item of the catalog. When the object comes from an external system, the key is built and provided by the connector.

Read more: Identification Keys

Object	Identifier Key	Description
Dataset	code/project/dataset name	code: Unique identifier of the connection noted in the configuration file project: Dataiku project name dataset name
Field	code/project/dataset name/field name	code: Unique identifier of the connection noted in the configuration file project: Dataiku project name dataset name field name