Skip to content

Commit

Permalink
chore: clarify proxy clients vs front-end clients
Browse files Browse the repository at this point in the history
  • Loading branch information
thomasheartman committed Apr 13, 2022
1 parent 5e382e6 commit 93d2ef5
Showing 1 changed file with 1 addition and 1 deletion.
2 changes: 1 addition & 1 deletion website/docs/reference/api-tokens-and-client-keys.mdx
Expand Up @@ -95,7 +95,7 @@ Some example client tokens are:

## Proxy client keys {#proxy-client-keys}

Use proxy client keys to connect [front-end client SDKs](../sdks/index.md#front-end-sdks) to the [Unleash Proxy](../sdks/unleash-proxy.md). As opposed to the [API tokens](#api-tokens), Proxy client keys are *not* considered secret and are safe to use on any clients (refer to the [the proxy documentation for more about privacy](../sdks/unleash-proxy.md#we-care-about-privacy)). They do _not_ let you connect to the Unleash server API.
Use proxy client keys to connect [Proxy client SDKs (front-end SDKs)](../sdks/index.md#front-end-sdks) to the [Unleash Proxy](../sdks/unleash-proxy.md). As opposed to the [API tokens](#api-tokens), Proxy client keys are *not* considered secret and are safe to use on any clients (refer to the [the proxy documentation for more about privacy](../sdks/unleash-proxy.md#we-care-about-privacy)). They do _not_ let you connect to the Unleash server API.

Proxy client keys are arbitrary strings that you *must* provide the Unleash proxy with on startup. Unleash does not generate proxy client keys for you. Because of this, they have no specific format.

Expand Down

0 comments on commit 93d2ef5

Please sign in to comment.