Join our Newsletter — 33% off our NHI Course
Home› Glossary› Identity Beyond IAM› Custom Tab
Identity Beyond IAM

Custom Tab

← Back to Glossary
By NHI Mgmt Group Updated November 2, 2026 Domain: Identity Beyond IAM

A Custom Tab is the browser backed sign in surface used by native Android apps to open an external authentication session. It shares the system browser cookie jar, which preserves existing login state and supports passkeys and password managers. It is preferred over an embedded WebView for identity flows.

What Custom Tabs Are Used For

A Custom Tab gives a native Android app a browser-backed authentication surface that lives outside the app’s own WebView. That matters because the user signs in through the system browser context, not an embedded page container, which preserves existing sessions and lets the browser handle modern identity features more reliably.

For native app sign-in, the design choice is usually less about appearance and more about trust boundaries. A Custom Tab reuses the browser’s authentication state, so a returning user can often continue with an established session, while the app receives the result of an external authentication flow rather than directly hosting the credentials exchange itself.

This is why Custom Tabs are commonly preferred in identity flows over embedded WebViews. The browser can support passkeys, password managers, and shared cookie state in a way that better aligns with modern authentication expectations, while keeping the sign-in experience anchored in the browser’s security model.

How Custom Tabs Fit Native App Authentication

In practice, a Custom Tab is part of the handoff between the app and the identity provider. The app initiates the sign-in journey, the browser handles the interactive authentication step, and the app then resumes after the browser-mediated session completes. That separation is important because it avoids making the app itself the primary venue for credential entry.

This pattern is especially relevant for OAuth-based native app sign-in, where the recommended approach is browser-based authorization rather than embedded login UI. NHIMG’s OAuth for Native and Mobile Apps Guide covers the browser-first model, including why system browsers are preferred over WebViews for native app authentication.

Because the browser owns the session state, a Custom Tab can participate in flows that depend on existing login context, password manager autofill, and passkey ceremonies. That makes it a practical identity surface, not just a rendering choice, and it is one reason developers should treat it as part of authentication design rather than a cosmetic UI decision.

Custom Tabs Versus Embedded WebViews

The core difference is where trust and session handling live. A Custom Tab uses the browser’s cookie jar and security features, while an embedded WebView places the sign-in experience inside the app’s own UI component. That distinction matters because the app does not get the same level of inherited browser protections when it embeds the flow itself.

NHIMG’s Mobile WebView Security Guide explains the controls and failure modes that arise when apps embed web content, including script bridges, file access and TLS handling. For identity flows, that background helps explain why a browser-backed tab is usually the safer default.

The practical takeaway is that a Custom Tab is usually chosen when the application needs an external authentication session with browser capabilities intact. A WebView may still be used for non-authentication web content, but it is a weaker choice when the flow depends on federated login, shared session state, or platform-native authenticator support.

Why Custom Tabs Matter for Identity Security

Custom Tabs improve the security posture of mobile sign-in by keeping authentication in the browser ecosystem that users already trust for sessions, cookies and credential handling. That reduces pressure on the app to replicate browser-grade identity behavior and makes it easier to support phishing-resistant and user-friendly sign-in methods.

They also help preserve the separation between application code and the authentication transaction. If the app were to capture or mediate credentials inside an embedded view, the attack surface would expand and the browser’s existing protections would be harder to rely on. A Custom Tab narrows that exposure by delegating the sensitive step to the browser context.

For organisations, that means the real question is not whether the tab is “custom”, but whether the app is using a browser-backed flow that preserves the protections expected of modern native app authentication. In that sense, Custom Tabs are a control choice as much as a UX choice.

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, NIST SP 800-53 Rev 5 and OWASP ASVS set the governance and control requirements practitioners need to meet.

FrameworkControl / ReferenceRelevance
NIST SP 800-63Digital Identity GuidelinesDefines phishing-resistant native app sign-in and browser-based federation patterns.
Recommendation — Prefer browser-based native app authentication flows that support phishing-resistant authenticators and shared session state.
NIST SP 800-53 Rev 5IA-9 — Service Identification and AuthenticationApplies when a native app and identity provider authenticate through a browser-backed session.
IA-5 — Authenticator ManagementSupports secure handling of credentials, tokens and related authenticator material used in sign-in flows.
Recommendation — Enforce browser-mediated authentication paths and validate trusted session handling for app sign-in. Protect credential lifecycle handling so app sign-in relies on managed authenticators rather than ad hoc secrets.
OWASP ASVSV10 — OAuth and OIDCCovers browser-based OAuth and OIDC flows used by native apps and the risks of embedded login handling.
Recommendation — Verify that native app sign-in uses approved OAuth and OIDC browser flows rather than embedded authentication UI.

Practitioner Guidance

Why practitioners should care: Use a Custom Tab when the sign-in flow needs browser-mediated state, modern authenticators, or a shared login context. It is the stronger default for native Android identity journeys because it aligns the app with the browser’s session and credential handling rather than recreating those behaviors inside the app.

Common misunderstanding: An embedded WebView can look convenient, but convenience is not the same as authentication safety. If the flow is truly an identity flow, the browser-backed model is usually the better operational choice.

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.

NHIMG Editorial Note
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