An application that cannot safely keep a client secret and therefore must be treated as externally visible in its trust model. For CLI tools, this usually means the app can initiate authorization but should not rely on hidden credentials for authentication. The security boundary shifts to scope control, token handling, and revocation.
What a public OAuth client is
A public OAuth client is one that cannot safely protect a client secret, so the trust model has to assume the software may be inspected, copied, or run in untrusted environments. That changes the security boundary from secret-based client authentication to safer authorization design, token handling, and revocation discipline.
That distinction matters because the client type determines which OAuth protections are realistic. A public client may still initiate authorization securely, but it should not be treated like a confidential server app that can keep long-term credentials hidden.
For the underlying framework, RFC 6749: The OAuth 2.0 Authorization Framework defines the core client model and the flows that public clients are designed to use.
Why public clients are treated differently from confidential clients
The key difference is credential storage, not intent. A desktop app, browser-based app, mobile app, or CLI tool may all be legitimate OAuth clients, but if the code or runtime cannot keep a shared secret hidden from the user or attacker, then that secret cannot be relied on for authentication.
That is why public clients are usually expected to use redirect-based authorization and stronger runtime protections rather than a fixed secret. In practice, the design goal is to limit what a stolen token can do, reduce the value of interception, and make client impersonation harder even when the client itself is exposed.
RFC 9700: Best Current Practice for OAuth 2.0 Security is the most useful authority for the modern security expectations around OAuth deployments, including sender-constrained tokens and resistance to token theft.
Common security mechanisms used with public OAuth clients
Because the client cannot keep a secret, the architecture shifts to controls that bind the authorization to a specific app instance, session, or proof of possession. PKCE is the best-known example for browser and native app flows, while sender-constrained tokens such as DPoP or mutual TLS can reduce replay risk when the deployment supports them.
Scope design becomes especially important. A public client should request only the minimum access needed, and the authorization server should treat token audience, redirect URI handling, and consent boundaries as part of the trust decision, not as optional convenience settings.
When the use case requires stronger client authentication than a shared secret can provide, RFC 7523: JWT Profile for OAuth 2.0 Client Authentication and Authorization Grants and RFC 8705: OAuth 2.0 Mutual-TLS Client Authentication and Certificate-Bound Access Tokens show alternative patterns that rely on stronger proof than a reusable secret.
Where public OAuth clients break down in practice
Public clients become dangerous when teams assume they can behave like server-side applications. If a secret is embedded in a mobile app, desktop tool, browser bundle, or automation script, the secret is usually recoverable and may be reused elsewhere. That turns a convenience shortcut into a credential exposure problem.
The other failure mode is overbroad access. Even when the client itself is public, the issued token may still reach sensitive APIs, long-lived sessions, or high-value user data. That means revocation, token lifetime, and consent review matter as much as the original login step.
For implementation details around token binding and audience restriction, RFC 9449: OAuth 2.0 Demonstrating Proof of Possession (DPoP) and RFC 8707: Resource Indicators for OAuth 2.0 are helpful references.
Public clients in modern identity and application security
Public client handling is now a core part of identity security for native apps, browser apps, and many developer tools. The practical question is not whether the client is “trusted” in the abstract, but whether its runtime can safely hold credentials and whether the authorization server can constrain the resulting tokens tightly enough for the risk involved.
That is why modern OAuth guidance increasingly favors short-lived tokens, explicit audiences, and proof-based protections over reusable secrets. It is also why teams should treat consent screens, redirect URIs, token storage, and revocation as security controls rather than just implementation details.
When you want the client model explained in the context of the broader OAuth ecosystem, OpenID Connect Core 1.0 provides the identity layer that is often paired with OAuth in public-client sign-in flows.
Standards & Framework Alignment
This section maps relevant standards and security frameworks to the operational risks and controls described in this guidance.
NIST SP 800-53 Rev 5, CIS Controls v8 and OWASP ASVS set the governance and control requirements practitioners need to meet.
| Framework | Control / Reference | Relevance |
|---|---|---|
| NIST SP 800-53 Rev 5 | IA-2 — Identification and Authentication (Organizational Users) | Public clients need stronger user auth and session controls around delegated access. |
| IA-5 — Authenticator Management | OAuth clients rely on token, secret, and credential lifecycle discipline. | |
| AC-6 — Least Privilege | Public clients should receive only the minimum scopes and access needed. | |
| Recommendation — Use IA-2 to enforce robust user authentication before issuing delegated tokens. Apply IA-5 to manage issuance, rotation, protection, and revocation of OAuth credentials. Use AC-6 to limit token scopes and downstream permissions to least privilege. | ||
| CIS Controls v8 | CIS-6 — Access Control Management | OAuth client access hinges on tightly governing account and token access paths. |
| Recommendation — Use CIS-6 to govern access, revoke stale grants, and limit token abuse paths. | ||
| OWASP ASVS | V10 — OAuth and OIDC | Public clients are a primary OAuth/OIDC implementation pattern with specific security requirements. |
| Recommendation — Apply V10 to verify OAuth client flows, redirect handling, and token protections. | ||
Related resources from NHI Mgmt Group
- Guide: OAuth 2.0 and OpenID Connect Guide for Identity Teams
- OAuth 2.0 Public Client
- How should security teams govern sender-constrained OAuth tokens for public clients?
- How should security teams use private_key_jwt for OAuth client authentication?
- How should security teams govern URL-based OAuth client identities in MCP?
Deepen Your Knowledge
Free weekly newsletter
Subscribe to the NHI & AI Identity Journal
The latest on NHI and Agentic AI security – articles, research, breaches, news and events every week.
Bonus 33% off our NHI Course when you subscribe.
Reviewed and updated by the NHIMG editorial team on November 2, 2026.
NHI Mgmt Group — the #1 independent authority on Non-Human Identity, IAM, and Agentic AI security. nhimg.org