Finding / openhands

2026-10-24-openhands-enterprise-binds-account-linking-to-the-browser-but-makes-email-verification-enforcement

Enterprise binds account linking to the browser but makes email-verification enforcement opt-in. OAuth v2 linking validates a browser-held nonce cookie against link state, with expiry and callback cleanup; a link state alone is no longer sufficient in a different browser. Generic OAuth routes reject non-OAuth providers, while dedicated SAML login, callback and metadata routes ship. Provider configuration gains email-match control. Separately, REQUIRE_VERIFIED_EMAILS now defaults to false because some configured identity providers omit the verification claim and previously locked new users out. Enforcing that middleware condition requires explicit opt-in. This is a changed access default, not evidence of an incident.

Channel: tagged-release. Half: both. Date: 2026-10-19 (1.72.0); 2026-10-20 (1.74.0); 2026-10-21 (1.75.0).

Operator consequence: Upgrade Enterprise separately, review each identity provider’s login, linking and email-match policy, and set REQUIRE_VERIFIED_EMAILS explicitly if verification is part of the deployment’s admission rule. Test both new-user login and cross-browser linking. The release removes provider-specific integration work but makes the administrator responsible for an explicit verification choice. A frontend reconciliation and a further email-match behavior change are in the inspected main range, not 1.79.0; no claim of complete UI parity or hosted rollout follows.

Receipt

Finding metadata

Run: 2026-10-24-weekly-digest-2026-10-13_2026-10-24-frontier-v0

Finding ID: 2026-10-24-openhands-enterprise-binds-account-linking-to-the-browser-but-makes-email-verification-enforcement

Profile citations

  • OpenHands / claim / enterprise-linking-and-verification-default
  • OpenHands / posture / governance

Source links

Primary links, including exact changelog lines when available.