Airflow Connection Profile Parameters

You must enable the remote REST API access to connect and use Control-M for Airflow, as described in Enabling Remote REST API Access.

The following table describes the Airflow connection profile parameters:

Parameter

Description

Host name

Defines the Airflow host name.

User name

Defines the username that is used to log in to the Airflow server.

Port

Defines the Airflow port number of the Airflow web server.

Password

Defines the password to log in to the Airflow server.

Secured connection (HTTPs)

Determines whether a secure connection to the Airflow server is established.

Valid Values:

  • True

  • False

Enabling Remote REST API Access

This procedure describes how to configure the Airflow server to accept REST API requests that are required by Control-M for Airflow.

Begin

  1. Log in to your Airflow server account.

  2. Open airflow.cfg and modify.

  3. Verify that the Airflow property auth_backend (auth_backends from version 2.3.0) has a value of airflow.api.auth.backend.basic_auth.

  4. Restart the Airflow server.

Importing an Airflow Server Certificate to Support HTTPS Connection

This procedure describes how to import an Airflow server certificate in the JRE cacerts file (trusted certificates store) for supporting HTTPS connection.

Begin

  1. Download the certificate from the Airflow server.

  1. Import the certificate file to the Control-M for Airflow JRE truststore, by running the following command:

    • Windows:<JRE>\bin\keytool -import -keystore <AG>\cm\AFL\data\security\apcerts -file <certificate file> -storepass <password, default is appass>

    • Linux:<JRE>/bin/keytool -import -keystore <AG>/cm/AFL/data/security/apcerts -file <certificate file> -storepass <password, default is appass>

    /home/agent/my_java/bin/keytool -import -keystore /home/agent/cm/AFL/data/security/apcerts -file airflow.cer -storepass appass

  1. Restart the Agent.