Glossary
client secret
A client secret is a password an app shares with the sign-in server to prove its identity. Public clients like onelifevibe-muse use PKCE instead.
Updated November 15, 2026
- Standard
- RFC 6749 (OAuth 2.0)
- Also called
app secret
At OneLifeVibe
- OneLifeVibe requires PKCE with the S256 method for the account connector. Meta Muse uses the public client onelifevibe-muse with PKCE and no client secret.
Related terms
What it means
In OAuth 2.0, a client secret is the password a registered app sends to the authorization server to prove it is the app it claims to be. It is also called an app secret. The server issues it when the app is registered.
Treat it like any other credential: keep it on the server, not in client-side code, and change it if it leaks. It belongs to confidential clients, which can keep a value private. Public clients cannot, because their code ships to browsers, phones or desktops. RFC 6749 covers OAuth 2.0 and the client types that use this credential.
How it works
The app authenticates with its client ID and client secret when it talks to the token endpoint. The server checks the pair, then decides whether to issue or refresh tokens. The secret is a shared credential, so anyone who has it can act as the app. Keep it out of URLs, logs and source control.
Public clients take a different path. They cannot hold a secret, so PKCE binds the authorization request to the token request with a code verifier and a code challenge. With the S256 method, the challenge is a SHA-256 hash of the verifier. An attacker who intercepts the authorization code still lacks the verifier.
If authentication fails, confirm the client ID, the secret value and the environment. A value from a test app will not match a production app. Rotate the secret after exposure and redeploy the server that uses it.
How OneLifeVibe uses it
OneLifeVibe requires PKCE with the S256 method for the account connector. The public client onelifevibe-muse has no client secret and relies on PKCE. Meta Muse uses that client with PKCE.
For Meta Muse, there is no app secret to send, store or rotate. The code verifier stays with the client for the token request, and the S256 challenge goes in the authorization request. The server checks the verifier against the challenge.
If you integrate with the account connector, build the S256 challenge from a verifier for each authorization request. Do not add a client secret to the public client flow. onelifevibe-muse has none.
Common mistakes
The most common mistake is putting a client secret in a browser, mobile app or desktop binary. Anyone who can read the code can read the secret. If the app cannot keep a value private, use a public client with PKCE.
Another mistake is treating the client ID as a secret. The client ID is public; the secret is the private half. Sending both in a URL or logging the token request leaks the secret.
With PKCE, do not skip the verifier check or reuse a verifier across flows. Use S256 where the server requires S256. If a request fails, fix the credential or verifier before retrying. Repeated retries with the same bad value will not help.
Questions
Does Meta Muse use a client secret?
No. Meta Muse uses the public client onelifevibe-muse with PKCE and no client secret.
What PKCE method does OneLifeVibe require for the account connector?
OneLifeVibe requires PKCE with the S256 method for the account connector. Use the S256 code challenge method in the authorization flow.
See it working. The OneLifeVibe connector and Platform API put these pieces together.
Written from the OneLifeVibe tool registry and platform configuration, and checked automatically before publishing. Something wrong? Tell us.