About the connector
Cloudera provides a scalable, flexible, integrated platform that makes it easy to manage rapidly increasing volumes and varieties of data in your enterprise.
This document provides information about the Cloudera EDH connector, which facilitates automated interactions, with a Cloudera EDH server using FortiSOAR™ playbooks. Add the Cloudera EDH connector as a step in FortiSOAR™ playbooks and perform automated operations, such as running a query on the Cloudera EDH database to fetch data from the Cloudera EDH, or retrieving a list of table names from the Cloudera EDH database.
Version information
Connector Version: 1.0.0
FortiSOAR™ Version Tested on: 5.1.0-464
Authored By: Fortinet
Certified: Yes
Installing the connector
From FortiSOAR™ 5.0.0 onwards, use the Connector Store to install the connector. For the detailed procedure to install a connector, click here.
You can also use the yum command to install connectors. Connectors provided by FortiSOAR™ are delivered using a FortiSOAR™ repository. Therefore, you must set up your FortiSOAR™ repository and run the yum command as a root user to install connectors:
yum install cyops-connector-cloudera-edh
Prerequisites to configuring the connector
- You must have the name of the Cloudera EDH server and Cloudera EDH database to which you will connect and perform automated operations and credentials and port number to access Cloudera EDH.
- To access the FortiSOAR™ UI, ensure that port 443 is open through the firewall for the FortiSOAR™ instance.
Configuring the connector
For the procedure to configure a connector, click here
Configuration parameters
In FortiSOAR™, on the Connectors page, select the Cloudera EDH connector row (if you are in the Grid view on the Connectors page), and in the Configurations tab enter the required configuration details.
| Parameter |
Description |
| Server Name |
Name of the Cloudera EDH server to which you will connect and perform the automated operations. |
| Database Name |
Name of the Cloudera EDH database to which you will connect and perform the automated operations. |
| Port |
Port number of HS2. The default port number if you are using the Impala (unsecured) authentication mechanism is 21050. The port number used for Hive will generally be different from the default port. |
| Username |
Username to connect to the Cloudera EDH database to which you will connect and perform the automated operations. |
| Password |
Password to connect to the Cloudera EDH database to which you will connect and perform the automated operations. |
| Auth Mechanism |
Select the authentication mechanism that you want to use to connect to Cloudera EDH database to which you will connect and perform the automated operations. Select from one of the following options:
- NOSASL: Select this option to connect using unsecured Impala.
- PLAIN: Select this option to connect using unsecured Hive because Hive requires SASL transport.
- GSSAPI: Select this option to connect using Kerberos
- LDAP: Select this option to connect using Kerberos with LDAP.
|
| Kerberos Service Name |
Name of the Kerberos Service used to authenticate to a particular ‘Impalad’ service principle. Uses ‘Impala’ by default. |
| Verify SSL |
Specifies whether the SSL certificate for the server is to be verified or not.
By default, this option is set as True. |
Actions supported by the connector
The following automated operations can be included in playbooks, and you can also use the annotations to access operations from CyOPsTM release 4.10.0 and onwards:
| Function |
Description |
Annotation and Category |
| Execute Select Query |
Executes a SELECT query on the connected Cloudera EDH database. |
select_query
Investigation |
| Run Query |
Executes a query on the connected Cloudera EDH database. |
run_query
Investigation |
| Get Table List |
Retrieves a list of all table names from the connected Cloudera EDH database. |
list_tables
Investigation |
| Get Columns |
Retrieves the list of columns for a specific table from the connected Cloudera EDH database based on the table name you have specified. |
list_columns
Investigation |
operation: Execute Select Query
Input parameters
| Parameter |
Description |
| Query |
SELECT query that you want to run on the Cloudera EDH database to fetch data from Cloudera EDH. |
Output
No output schema is available at this time.
operation: Run Query
Input parameters
| Parameter |
Description |
| SQL Query |
SQL query that you want to run on the Cloudera EDH database to fetch data from Cloudera EDH. |
Output
The output contains the following populated JSON schema:
{
"message": ""
}
operation: Get Table List
Input parameters
None.
Output
No output schema is available at this time.
operation: Get Columns
Input parameters
| Parameter |
Description |
| Table Name |
Name of the table whose columns you want to retrieve from the connected Cloudera EDH database. |
Output
No output schema is available at this time.
Included playbooks
The Sample - Cloudera EDH - 1.0.0 playbook collection comes bundled with the Cloudera EDH connector. These playbooks contain steps using which you can perform all supported actions. You can see bundled playbooks in the Automation > Playbooks section in FortiSOAR™ after importing the Cloudera EDH connector.
- Execute Select Query
- Get Columns
- Get Table List
- Run Query
Note: If you are planning to use any of the sample playbooks in your environment, ensure that you clone those playbooks and move them to a different collection since the sample playbook collection gets deleted during the connector upgrade and delete.
