> For the complete documentation index, see [llms.txt](https://docs.pentaho.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.pentaho.com/install/10.2-install/pentaho-configuration/tasks-to-be-performed-by-an-it-administrator/set-up-the-pentaho-server-to-connect-to-a-hadoop-cluster/additional-configurations-for-specific-distributions-connecting-to-a-cluster/advanced-settings-for-connecting-to-azure-hdinsight-cp/before-you-begin-hdi/set-up-a-secured-instance-hdi.md).

# Set up a secured instance

If you are connecting to HDI secured with Kerberos, you must also perform the following tasks.

1. Configure Kerberos security on the platform, including the Kerberos Realm, Kerberos KDC, and Kerberos Administrative Server.
2. Configure the following items to accept remote connection requests:
   * Name
   * Data
   * Secondary
   * Job tracker
   * Task tracker nodes
3. If you have deployed HDI using an enterprise-level program, set up Kerberos for name, data, secondary name, job tracker, and task tracker nodes.
4. Add user account credentials to the Kerberos database for each Pentaho user that needs access to HDI.
5. Verify that an operating system user account exists on each node in HDI for each user you want to add to the Kerberos database. Add operating system user accounts if necessary.

   **Note:** The user account UIDs should be greater than the minimum user ID value (**min.user.id**). Usually, the minimum user ID value is set to `1000`.
6. Set up Kerberos on your Pentaho machines.See the **Administer Pentaho Data Integration and Analytics** document for instructions.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

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

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.pentaho.com/install/10.2-install/pentaho-configuration/tasks-to-be-performed-by-an-it-administrator/set-up-the-pentaho-server-to-connect-to-a-hadoop-cluster/additional-configurations-for-specific-distributions-connecting-to-a-cluster/advanced-settings-for-connecting-to-azure-hdinsight-cp/before-you-begin-hdi/set-up-a-secured-instance-hdi.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.