Observed Signal · May 21, 2026 · Technical Release · Source: https://developer.chrome.com/static/blog/feed.xml · Impact: 4/5 · Sentiment: Positive
Chrome modernizes web authentication with passkeys, EVP
At Google I/O 2026, the Chrome team published guidance and platform updates to modernize web authentication, emphasizing passkeys, federated sign-up, and browser-mediated verified attributes. Key technical features covered include the FedCM API for identity federation, the experimental Email Verification Protocol (EVP) for seamless verified email claims, the Digital Credentials API for selective disclosure from wallets, Immediate UI Mode (shipped in Chrome 149) and passkey autofill/conditional create for zero-friction enrollment, and Device Bound Session Credentials (DBSC) to tie sessions to hardware (experimental on Windows). The post describes patterns (e.g., "federate-then-upgrade"), cross-platform credential sharing (Digital Asset Links and Related Origin Requests), and recovery strategies, and cites case studies (pixiv, adidas) showing improved login success and passkey adoption.
Major platform (Google/Chrome) publishing technical identity updates and shipping features (Immediate UI Mode, FedCM, DBSC) influences authentication patterns, conversion, and the identity layer used by web and app ecosystems—affecting how first‑party login signals and privacy-preserving verification can be used across the advertising ecosystem.
Track Google Signals & Market Shifts in Real-Time
Polaris7 autonomous intelligence agents track regulatory filings, primary sources, executive changes, and deal flow 24/7. Create your free Explorer workspace to monitor these entities.
Key Takeaways & Evidence Grounding
- Chrome Developers blog post published by Google on 2026-05-21 summarizing Google I/O 2026 identity guidance.
- FedCM API recommended for identity federation to provide one-tap sign-in and privacy-preserving browser UI.
- Email Verification Protocol (EVP) is an emerging, experimental browser feature to obtain verified email claims from issuers.
- Immediate UI Mode for credential mediation is available from Chrome 149 to enable proactive one-tap sign-ins; Conditional Create enables automatic passkey creation during login.
- Device Bound Session Credentials (DBSC) is an experimental feature (available on Windows) to bind sessions to hardware and mitigate session hijacking.
Connected Companies & Entities
2 Entities mappedOntology Mapping & Concepts
Related Market Signals & Shifts
Recent verified developments and strategic activity across this market segment.
Google tests browser email verification to ease signups
Google is testing an Email Verification Protocol (EVP) in Chrome that allows the browser to verify a user controls an email address without sending a one-time password or magic link. Available via Chrome’s Origin Trial, EVP delivers cryptographic proof from the user’s email provider directly to websites, keeping verification inside the browser and falling back to traditional methods when a provider does not support the protocol. Google’s support could accelerate adoption given Chrome’s market share and Google’s position in email. Marketers could see higher sign-up conversion rates and improved first-party data quality. EVP is part of a broader shift toward browser-managed identity alongside passkeys and Federated Credential Management (FedCM).
Chrome 148 Adds Immediate UI Mode for Sign-In
Chrome 148 introduces Immediate UI mode, a new WebAuthn-related capability that streamlines sign-in by letting the browser proactively offer saved passkeys and managed passwords via an immediate login dialog. Sites can invoke an inline prompt (for example on a Sign In or Checkout button) to request credentials without redirecting to a separate login page or showing a form. If no credentials are available, the API rejects the request silently so sites can fall back to existing authentication methods. The feature replaces the origin-trial API behavior: developers should now set uiMode: 'immediate' in navigator.credentials.get(). The announcement was published on May 12, 2026 by Eiji Kitamura and José Luis Zapata on the Chrome Developers blog.
Chrome 143 Enhances FedCM for Better Privacy and Consistency
Chrome 143 introduces updates to the Federated Credential Management (FedCM) API to improve privacy, developer experience, and interoperability. Key changes include support for structured JSON objects in the ID assertion endpoint token, stricter validation requirements for IdP endpoints (including requiring accounts_endpoint and login_url in .well-known/web-identity), and API consistency/error-handling updates such as relocating the nonce into the params object and renaming IdentityCredentialError.code to IdentityCredentialError.error. Several changes are enforced in later versions (Chrome 145 for accounts_endpoint enforcement, nonce relocation, and the renamed error property). The post provides migration guidance for Chrome 143–144 compatibility, links to implementation guides and a FedCM demo, and invites feedback via the project's GitHub and developer newsletter.
Track Real-Time Market Signals & Shifts
Set up custom watchlists to receive automated, evidence-grounded executive digests whenever material signals or shifts occur across your tracked landscape.