> For the complete documentation index, see [llms.txt](https://docs.balkan.id/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.balkan.id/getting-started/setting-up-your-tenant/application-integrations/direct-application-integrations/harness-integration-setup.md).

# Harness Integration Setup

### Getting Started <a href="#h_01h9kzjybek4temypa6a5ffh7w" id="h_01h9kzjybek4temypa6a5ffh7w"></a>

BalkanID recommends creating a separate service account for the purposes of this integration, instead of using personal or employee named accounts.

#### Requirements: <a href="#h_01hq31hmzdrvcyk70k44ey6dv5" id="h_01hq31hmzdrvcyk70k44ey6dv5"></a>

A Harness API key has exactly the access of the service account or user it belongs to, hence it is advised to grant it account-level read access across all child scopes.

* ***API Key -*** An API key token generated for the service account in Harness.
* ***Account ID -*** Your Harness account identifier.
* ***Base URL -*** The Harness API base URL. Defaults to `https://app.harness.io` for Harness SaaS; override this only for a self-managed installation.

#### Getting the Configuration <a href="#h_01h9kzjybeacehzfkaw2cz10mj" id="h_01h9kzjybeacehzfkaw2cz10mj"></a>

1. Sign in to Harness at `https://app.harness.io` as an Account Admin.
2. Go to **Account Settings** > **Access Control**, select **Service Accounts** in the header, and click **New Service Account**. Enter a Name and Email for it, then click Save.
3. Select **Manage Roles** next to the new service account, click Add, and assign the **Account Admin** role with the **All Resources Including Child Scopes** resource group.

   <div data-with-frame="true"><figure><img src="https://2975852473-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FbVGYwk8aSk5yI1GDPEW9%2Fuploads%2FrN2LKP0puBMfQj4Y4Opd%2Fimage.png?alt=media&amp;token=88a666a4-4b6d-4a14-b897-ce0fd67b3a68" alt=""><figcaption></figcaption></figure></div>
4. Under **API Keys** on the service account, select **API Key**, enter a **Name**, and click **Save**. Then select **Token** under the new API key, enter a **Name**, and click **Generate Token**. This is your **API Key**.<br>

   <div data-with-frame="true"><figure><img src="https://2975852473-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FbVGYwk8aSk5yI1GDPEW9%2Fuploads%2FyCrfHphsY0eA267xqSP9%2Fimage.png?alt=media&amp;token=79a99781-c601-4585-9f04-a016193a01f5" alt=""><figcaption></figcaption></figure></div>
5. For **Account ID**, copy the value from any Harness URL:\
   `https://app.harness.io/ng/account/<ACCOUNT_ID>`

### Configure integration within your BalkanID tenant <a href="#h_01h9kzjybf182sj7n8mrydhrdt" id="h_01h9kzjybf182sj7n8mrydhrdt"></a>

1. Login to the BalkanID application and switch to the tenant you would like to add your integration to.
2. Head to *Integrations* > **Add Integration**, select **Harness**.

   <div data-with-frame="true"><figure><img src="https://2975852473-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FbVGYwk8aSk5yI1GDPEW9%2Fuploads%2FXRvzAfUdpqlc7iQZT5Na%2Fimage.png?alt=media&amp;token=43dd9897-4221-45f6-b341-f15fd50fa14a" alt=""><figcaption></figcaption></figure></div>

   <div data-with-frame="true"><figure><img src="https://2975852473-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FbVGYwk8aSk5yI1GDPEW9%2Fuploads%2FPOT3vgbcOJ7q5QJq8M1M%2Fimage.png?alt=media&amp;token=7f8e43b8-f8a5-4009-bc24-9ea866b8ee14" alt=""><figcaption></figcaption></figure></div>
3. Set up the *Primary Application owner (mandatory)* and the *Description*, if any. Set up Secondary Application Owner(s), if any.<br>

   Select the Extraction Type. From here, you can configure your application using one of the following methods:

   1. **Direct integration** - Provide the API Key, Account ID and Base URL obtained above to set up a direct connection with BalkanID.
   2. **SCIM integration** - Provide SCIM server credentials to set up a SCIM connection with BalkanID.
   3. **Manual file upload** - Upload Entity and Entity Relations through a .CSV file upload. Contact the team for assistance with this.<br>

      <div data-with-frame="true"><figure><img src="https://2975852473-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FbVGYwk8aSk5yI1GDPEW9%2Fuploads%2FXU8ARnFrgqgdbGHNm9bp%2Fimage.png?alt=media&amp;token=06ac4d31-4c9a-4230-b6d2-9785a96536ad" alt=""><figcaption></figcaption></figure></div>
4. Click on next to move onto *Optional Configuration.*
5. Fill **Optional configuration,** if required.

   <figure><img src="https://2975852473-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FbVGYwk8aSk5yI1GDPEW9%2Fuploads%2FWwMwzBtDCwYSplMbZBtP%2Fimage.png?alt=media&amp;token=0d22f002-4d7b-4d31-84c0-31b50ca63edd" alt="" width="563"><figcaption></figcaption></figure>
6. Once you filled in the information, click **Save**. Your integration is now configured and you will see the status of the integration displayed alongside other integrations on the *Integrations* page. When data is available, the integration Status will read **Connected** and the integration Message will read **Data available**.


---

# 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.balkan.id/getting-started/setting-up-your-tenant/application-integrations/direct-application-integrations/harness-integration-setup.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.