> For the complete documentation index, see [llms.txt](https://docs.dckapintegrator.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.dckapintegrator.com/project-manager/systems/credentials.md).

# Credentials

This is where the user will configure the system credential details. These credentials will be used by the Integration pipes to access data in a system.

* [Add/Edit Credential](#add-edit-credential)
* [Reuse Token in Test Connection](#reuse-token-in-test-connection)
* [Server Health Checkup](#server-health-check-up)

## Add/Edit Credential

From the Credentials section on the systems page, click on **Add New Credential** to create new credential details: 

<figure><img src="https://2655769465-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-LjVABEcCgwItwY4IEAD%2Fuploads%2F73T21zVutf2Bf7LtQbxF%2FGlobal%20system%20overview.png?alt=media&amp;token=329e6307-4101-4adc-85ee-37591cb0fe67" alt=""><figcaption></figcaption></figure>

Provide the following fields:&#x20;

<table data-header-hidden><thead><tr><th width="186.5">Field Name</th><th>Description</th></tr></thead><tbody><tr><td>Field Name</td><td>Description</td></tr><tr><td>Name</td><td>Enter a suitable name for your Credential details</td></tr><tr><td>Hostname</td><td><p>Enter your system URL in the format.</p><p><code>https://www.domainname.com</code></p></td></tr><tr><td>Timezone</td><td>Select the target system server timezone. This will be used to fetch data based on the respective timezone.</td></tr><tr><td>Secure Keys</td><td>Provide secure keys depending on the system chosen</td></tr></tbody></table>

{% hint style="danger" %}
*Do not include a slash at the end while providing Hostname*
{% endhint %}

Click on **Submit** to save the credential details. Once added, [test the connection](/project-manager/systems/credentials.md#test-connection) to ensure that proper credential details are provided.

## Reuse Token in Test Connection

{% hint style="success" %}
*Test connection is used to validate the provided credentials by making an authorized connection to the target system.*
{% endhint %}

When the test connection button is clicked, DCKAP Integrator generates a token and reuses it. This token can be reused till it's valid. Users have the ability to test with a fresh token or with an existing token.

* Test with Fresh Token: DCKAP Integrator will generate a new token for testing the connection.
* Test with Existing Token: DCKAP Integrator will use the previously generated token for testing the connection with the system.&#x20;

## Server Health Check-up

The Server Health Check-up is used to check the status of the server (Available or Down) by pinging the server at regular intervals. If the server is down/not available during the ping, DCKAP Integrator will notify the Project Owner and Admin via email.

<figure><img src="https://2655769465-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-LjVABEcCgwItwY4IEAD%2Fuploads%2F7ZlFUYVWDrYt6JvWrONB%2FServer%20Health%20Check%20up.png?alt=media&amp;token=1bd4db37-0cd5-44b1-9fb7-7694da0317b7" alt=""><figcaption></figcaption></figure>

Click `Configure` in the respective credential row in the credentials section.

Provide the values to the below fields

* Checker Status: Setting this to Yes will enable the Server Health Check-up.
* Ping Interval: The frequency of checkups


---

# 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.dckapintegrator.com/project-manager/systems/credentials.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.