# Client Secret

Every client gets a **Client ID** and a **Client Secret** generated at time of [Setup](/tng-identity-documentation/tng-identity-sso/the-sso-dashboard/clients/client-setup.md). The secret is an opaque token, a secret string. It must be stored securely on the client side. Exposing it may provide access to an attacker to pose as the client. 

The ID and secret have to be passed as Basic Auth in the OAuth authorization flow when exchanging the authorization code for a JWT access token.

<figure><img src="/files/DKAtkrO4kYHVMRCz0G3L" alt=""><figcaption><p>Showing a Client ID and Client Secret at client setup time</p></figcaption></figure>

### Secret Regenerate

The **Client Secret** is generated and shown only at setup time. You must copy and store the secret securely. The SSO service stores only a **hash of the secret**, so if lost, it has to be regenerated.

<figure><img src="/files/d0Qwi0VBhausPg5jVxpD" alt=""><figcaption></figcaption></figure>

<figure><img src="/files/AZgY7sCVHtrKmQuUYcsh" alt=""><figcaption></figcaption></figure>

<figure><img src="/files/m6e9HEonJtkMWgNmH2TC" alt=""><figcaption></figcaption></figure>


---

# 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.teranode.group/tng-identity-documentation/tng-identity-sso/the-sso-dashboard/clients/client-secret.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.