# Specify Kerberos security

Perform the following steps to specify the credentials for the Kerberos security.

**Note:** You can define different principal users for each of the named connections only if all the clusters for these connections are in the same Kerberos realm. See [MIT Kerberos Documentation](https://web.mit.edu/kerberos/krb5-devel/doc/admin/realm_config.html) for more information about Kerberos realms.

1. Select **Kerberos** as the security type.
2. Click **Next**.
3. Choose one of the following security methods and specify the Kerberos credentials you obtained from the cluster administrator:
   * **Password**: Specify the **Authentication username** and **Password** options. Additionally, if you are connected to the Pentaho Repository and are using secure impersonation, specify the **Impersonation username** and **Password**. See **Try Pentaho Data Integration and Analytics** if the environment requires advanced settings, the server is on Windows, or when you are using a Cloudera Impala database for secure impersonation.

     ![Edit Cluster dialog box - Password option](/files/PB3EbsozJIQmxAZfMaGj)
   * **Keytab**: Specify the **Authentication username** and **Authentication Keytab** options. Click **Browse** to navigate to your keytab file. Additionally, if you are connected to the Pentaho Repository and are using secure impersonation, specify the **Impersonation username** and **Impersonation Keytab**. See **Try Pentaho Data Integration and Analytics** if the environment requires advanced settings, the server is on Windows, or when you are using a Cloudera Impala database for secure impersonation.

     ![Edit Cluster dialog box - Keytab option](/files/meG1fUmDiZQ30SU6y4MR)
4. Click **Next** to test the connection. See [Test a cluster connection](/pdia-data-integration/extracting-data-into-pdi/connecting-to-a-hadoop-cluster-with-the-pdi-client-article/adding-a-cluster-connection-connect-to-a-hadoop-cluster-with-the-pdi-client/test-the-cluster-connection-add-hadoop-cluster-connection.md) for more information.

   The **Test results** dialog box appears.

   ![Test results dialog box](/files/vOPlGR08j0y4aIeihtm8)

   For each tested connection, the dialog box displays one of the following icons to indicate the results:

   * ![Green checkmark symbol](/files/pIjuHzec0hjVNKMH4bgm) A green checkmark indicates the connection to the cluster service was successful.
   * ![Yellow caution symbol](/files/EHhwnoZCVZd6BbdKymoH) A yellow caution symbol indicates the cluster service information was not supplied, so the test for that component was skipped.
   * ![Red circle-backslash symbol](/files/uTInfJdW8NeFiCItaBSW) A red circle-backslash indicates the connection failed. Check the connection information and then test the connection again. If you suspect a different issue, see the troubleshooting section in the **Install Pentaho Data Integration and Analytics** document or consult the cluster administrator.**Note:** You can click the drop-down arrow in the **Hadoop file system** test for more details.
5. Click **Finish**.

If no errors occur during the connection, PDI is successfully connected.

If you have errors, see the troubleshooting section in the **Administer Pentaho Data Integration and Analytics** document to resolve the issues or consult the cluster administrator, then run the test again. When no error messages are returned, the connection is properly configured.


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.pentaho.com/pdia-data-integration/extracting-data-into-pdi/connecting-to-a-hadoop-cluster-with-the-pdi-client-article/adding-a-cluster-connection-connect-to-a-hadoop-cluster-with-the-pdi-client/secure-cluster-connections-add-hadoop-cluster-connection/kerberos-security-type-secure-hadoop-cluster-connections-in-pdi.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.