A public client is an application that runs in an environment the operator does not fully control, such as a browser, phone, or desktop device. Because users can inspect its code and runtime, it cannot safely hold secrets that require custody, confidentiality, or reliable rotation.
What Makes a Public Client Different
A public client is a client application that runs in a user-controlled environment, so the operator cannot assume custody of its code, runtime, or any embedded credentials. That changes the security baseline immediately: the client can still request tokens, but it cannot be treated as a trusted place to store long-lived secrets.
For identity systems, the practical distinction is between software that can be shipped to end users and software that can safely prove its own identity without exposing reusable secret material. In OAuth terms, this is why public clients are designed around flows that avoid sharing a static client secret with the browser, phone, or desktop application itself.
Why Public Clients Cannot Safely Hold Secrets
The core constraint is not that the application is “less secure” in a vague sense, but that users and attackers can inspect, copy, instrument, or modify what runs locally. If a secret is embedded in the app, it is exposed to extraction, replay, and reuse. That means a public client cannot reliably protect credentials that depend on confidentiality, exclusive custody, or controlled rotation.
This limitation matters for authorization design, because a secret that is safe in a back-end service may become unsafe when moved into a distributed client. The right control choice is therefore to avoid giving the public client a secret that would be treated as proof of trusted, exclusive possession.
Common Security Patterns for Public Clients
Public clients are usually paired with security patterns that shift trust away from client-held secrets and toward protocol features such as redirect-based authorization, PKCE, scoped tokens, and audience restriction. The client proves possession of a transaction-specific value or follows a user-mediated flow, rather than presenting a static credential that can be copied once and reused indefinitely.
That design also changes how token endpoints and authorization servers should interpret the client. A public client may still be authenticated in a protocol sense, but not by a secret that only the application is supposed to know. The security goal is to reduce the value of code inspection and runtime tampering by making the most sensitive material short-lived, bounded, or externally validated.
Where Public Clients Fit in Identity Architecture
Public clients are common in browsers, mobile apps, and many desktop applications, so they are a normal part of modern identity architecture rather than an edge case. The key decision is whether the application is a public client or a confidential client, because that classification determines whether secret-based client authentication is appropriate.
That distinction is central to secure OAuth design, and the OAuth 2.0 and OpenID Connect Guide for Identity Teams is the right companion reference for the grant types, PKCE, and client-type choices that flow from it.
Risk and Threat Considerations
Public clients create risk when teams mistakenly embed reusable secrets, treat the application as a trusted execution environment, or assume local storage is equivalent to server-side custody. Once a secret is exposed in a browser, phone, or desktop binary, attackers can extract it and reuse it outside the intended device or session.
Failure mechanism: The attacker or user obtains the embedded secret, copies it from code, memory, logs, or local storage, and reuses it to impersonate the client or extend access beyond the intended trust boundary.
Impact: The result can be token theft, unauthorized API access, broken client authentication, and broader abuse of any downstream authorization model that assumed the client could safely protect a secret.
Standards & Framework Alignment
This section maps relevant standards and security frameworks to the operational risks and controls described in this guidance.
NIST SP 800-63, OWASP ASVS, CIS Controls v8 and NIST SP 800-53 Rev 5 set the governance and control requirements practitioners need to meet.
| Framework | Control / Reference | Relevance |
|---|---|---|
| NIST SP 800-63 | Digital Identity Guidelines | Defines client-auth and assurance patterns for public client identity flows |
| Recommendation — Use phishing-resistant, redirect-based client flows that do not rely on client-held shared secrets. | ||
| OWASP ASVS | V10 — OAuth and OIDC | Covers OAuth/OIDC client behavior, grant choice, and public-client security requirements |
| Recommendation — Apply OAuth and OIDC verification requirements that avoid exposing reusable client secrets in public apps. | ||
| CIS Controls v8 | CIS-6 — Access Control Management | Supports restricting and reviewing access paths when client trust is limited |
| Recommendation — Restrict client capabilities to the minimum access needed and review exposed application credentials regularly. | ||
| NIST SP 800-53 Rev 5 | IA-5 — Authenticator Management | Addresses credential lifecycle risks when secrets cannot be safely retained by the client |
| Recommendation — Manage authenticators so public clients do not store long-lived reusable secrets. | ||
Practitioner Guidance
Why practitioners should care: Classify the application correctly before you choose an authentication pattern. If the software runs where the operator cannot enforce custody, do not design it around a shared secret, even if that secret would be acceptable in a server-side integration.
Common misunderstanding: Many teams treat “installed on a laptop” or “distributed through an app store” as if that created trustworthy secret storage. It does not, because the attacker model still includes code inspection, instrumentation, extraction, and replay.
Practitioner takeaway: For public clients, prefer flows and controls that assume the client can be observed and modified, and reserve secret-based client authentication for environments that can genuinely protect the secret.
Related resources from NHI Mgmt Group
- What breaks when public TLS certificates stop supporting client authentication?
- When should organisations use private PKI instead of public certificates for client auth?
- How should security teams handle client-auth certificates in public CA environments?
- Why do public-trust machine and client certificates create more operational risk than private PKI in BFSI environments?
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 1, 2026.
NHI Mgmt Group — the #1 independent authority on Non-Human Identity, IAM, and Agentic AI security. nhimg.org