Skip to content

Desktop browser blocks Local Network Access, so Okta Verify sign-in fails #5191

Open

Description

@koenvangeert

Summary

Okta sign-in fails in the bb browser. Okta Verify talks to a local app through localhost. Chromium needs the "Local network access" permission for that. The bb browser session denies every permission except clipboard-sanitized-write, so the request fails at once. The user has no site settings where they can allow it.

Versions and environment

  • bb 0.45.0 (desktop app), Electron 44.3.0
  • macOS 26.6.2
  • Okta Verify desktop app installed

Steps to reproduce

  1. Open a bb browser tab.
  2. Go to an Okta-protected sign-in page that uses Okta Verify (FastPass).
  3. Choose to sign in with Okta Verify.

Expected vs actual

Unable to sign in
The browser is blocking communication with Okta Verify.
Go to your browser's site settings
Find "Local network access" or "Apps on device"
Change the permission from "Block" to "Allow" and reload this page

Expected: Okta Verify opens and sign-in completes, as it does in Chrome.

Evidence

Allowlist on main:

function isAllowedBrowserPermission(permission: string): boolean {
return permission === "clipboard-sanitized-write";
}

It is used for both handlers:

browserSession.setPermissionRequestHandler((_wc, permission, callback) => {
callback(isAllowedBrowserPermission(permission));
});
browserSession.setPermissionCheckHandler((_wc, permission) =>
isAllowedBrowserPermission(permission),
);

What you ruled out

Possible fix

Allow local-network-access (and the related loopback permission), or prompt the user for each origin. An allowlist (for example *.okta.com) would also work.

Workaround

Sign in with Chrome, quit Chrome, then copy the cookies with bb browser import-cookies. You must do this again when the session expires.

AGENT GENERATED

Activity

  1. added theissue type on Oct 8, 2026
  2. added
    desktopDesktop app, install, update, packaging
    securityOperator trust, permission enforcement
    partial-reproBug partially reproduced; some claims unverified; see linked report
    on Oct 8, 2026
  3. bb-slop-cop commented on Oct 8, 2026

    @bb-slop-cop
    Contributor

    🚨 SLOP COP 🚨 · new-issue-autopilot

    • Classification: Bug · Priority: Medium · Effort: Medium · labels: desktop, security, partial-repro.
    • Report: https://get-bb.github.io/reports/issues/5191.html
    • Verdict: PARTIALLY REPRODUCED · root-cause confidence: high for the permission denial. The macOS/Okta Verify sign-in flow was not available to test.
    • Root cause: Both desktop browser session handlers grant only sanitized clipboard writes, denying local-network and loopback permissions without an origin consent path.
    • Reproduction: Three focused cases fail identically in two clean checkouts of trusted origin/main; the unchanged manager suite passes all 77 tests. Reproduction label: partial-repro.
    • No PR: A repair changes a permission/security boundary and requires a policy decision, so it is outside the automatic simple-fix rules.
  4. benwaffle commented on Oct 16, 2026

    @benwaffle

    The fix is small: add local-network-access, local-network, and loopback-network to the permission allowlist in isAllowedBrowserPermission (apps/desktop/src/desktop-browser-view.ts), which backs both session permission handlers. The change itself is a few lines.

    Reference: benwaffle@72199b7. It is a commit on a fork branch that gets rebased daily, so the link may move.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    desktopDesktop app, install, update, packagingpartial-reproBug partially reproduced; some claims unverified; see linked reportsecurityOperator trust, permission enforcement

    Type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions