Add Lexbox login to the Platform.Bible lexicon extension

[imnasnainaec]

Adds sign-in to Lexbox from the Platform.Bible lexicon extension, unblocking future account-based features (remote project listing, download, send/receive — out of scope here per the issue).

Uses the system-browser OAuth flow (--Auth:SystemWebViewLogin=true, same as FW Lite desktop): MSAL opens the user's default browser and listens on a localhost redirect, avoiding the webview-sandbox / frame-ancestors CSP unknowns an embedded login page would hit.

• FwLiteWeb: new GET /api/auth/login-web-view/{authority} endpoint that invokes AuthService.SignInWebView when SystemWebViewLogin is enabled and returns the LoginResult. The existing /login/{authority} endpoint is redirect-based and requires a Referer header, so it doesn't fit this mode; it still throws NotSupportedException there.
• Extension: FwLiteApi gains getAuthServers()/login()/logout(); new lexicon.authServers, lexicon.login, and lexicon.logout commands; the Select Lexicon webview shows each configured server's sign-in status with a Log in / Log out button, including a pending state while the browser sign-in is in flight.

Design points for review:

• Sign-in can outlive the 30s PAPI request timeout. login-web-view blocks until the user finishes or cancels in the browser; if that exceeds platform.requestTimeout (default 30s) the command reply times out even though sign-in still completes. The webview refreshes status on timeout, so a sign-in that lands shortly after usually still shows up — but one finishing well after won't surface until the webview reopens. The timeout also only rejects the webview→host command: the underlying HTTP request to FW Lite stays open (no server-side timeout), so repeatedly triggering and abandoning sign-in leaves pending requests on the FW Lite process until each browser flow resolves. A durable fix is server-side (a timeout/cancellation on the endpoint, or honoring request cancellation), not client-side. Is refresh-on-timeout good enough for now, or is a per-request-type timeout (via paranext-core's shared store) or polling worth it?
• External login-state changes aren't pushed to the webview. It fetches status on open and after its own login/logout only, so a sign-in/out done elsewhere (e.g. the embedded viewer) won't reflect until reopen. Acceptable for now, or worth a subscription?
• Local API hardening before shipping. FwLiteWeb still runs with --FwLiteWeb:CorsAllowAny=true on a fixed localhost port; now that users can be signed in, that local API is more sensitive. Not addressed here — flagged for follow-up.
• Non-success sign-in outcomes are logged, not shown. lexicon.login now returns the LoginResult and the webview logs a warning for a non-success/non-cancel outcome (e.g. Offline), but shows no targeted user-facing message. Is a visible "you appear to be offline" / failure notice wanted, or is the silent status refresh enough?

Testing note: FwLiteWeb's production config registers only https://lexbox.org; testing a packaged extension against staging needs extra --Auth:LexboxServers:* args.

Closes #2426

🤖 Generated with Claude Code

[coderabbitai]

Important

Review skipped

Draft detected.

Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

⚙️ Run configuration

Configuration used: Repository UI

Review profile: CHILL

Plan: Pro

Run ID: 2305f2cd-8dd9-43cb-a829-2a6402479177

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

• 🔍 Trigger review

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch pb-ext-lexbox-login

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands.}

[argos-ci]

The latest updates on your projects. Learn more about Argos notifications ↗︎

Build	Status	Details	Updated (UTC)
default (Inspect)	✅ No changes detected	-	Jul 9, 2026, 7:23 PM

[hahn-kev]

this looks good to me. One thing you should watch out for is fetch timeouts. If the user isn't logged in to lexbox (likely) then it might take them a while to login to lexbox, so a normal 30s timeout for a fetch might timeout. This isn't a problem on FW Lite because the browser path uses redirect, and the desktop path doesn't trigger the web view login via fetch so it can await forever.