Repository navigation
Desktop browser blocks Local Network Access, so Okta Verify sign-in fails #5191
Description
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
- Open a bb browser tab.
- Go to an Okta-protected sign-in page that uses Okta Verify (FastPass).
- 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:
bb/apps/desktop/src/desktop-browser-view.ts
Lines 420 to 422 in 53c1e87
| function isAllowedBrowserPermission(permission: string): boolean { | |
| return permission === "clipboard-sanitized-write"; | |
| } |
It is used for both handlers:
bb/apps/desktop/src/desktop-browser-view.ts
Lines 544 to 549 in 53c1e87
| browserSession.setPermissionRequestHandler((_wc, permission, callback) => { | |
| callback(isAllowedBrowserPermission(permission)); | |
| }); | |
| browserSession.setPermissionCheckHandler((_wc, permission) => | |
| isAllowedBrowserPermission(permission), | |
| ); |
What you ruled out
- Plugins can't fix this: the SDK can't change the session permission handlers.
- Not Provide a user-approved local file upload path for browser automation #3357 or Codex Browser Use approvals are auto-declined in accept-edits mode (no interaction shown) #4645: those are about file upload and Codex approvals.
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
bb-slop-cop commentedon Oct 8, 2026
🚨 SLOP COP 🚨 ·
new-issue-autopilotdesktop,security,partial-repro.origin/main; the unchanged manager suite passes all 77 tests. Reproduction label:partial-repro.benwaffle commentedon Oct 16, 2026
The fix is small: add
local-network-access,local-network, andloopback-networkto the permission allowlist inisAllowedBrowserPermission(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.