Repository navigation
Description
Problem or use case
Orca Mobile already supports user-managed remote endpoints through the custom network address / reverse-proxy path, and related issues track making Cloudflare Tunnel and other BYO tunnel options first-class.
One missing piece is edge authentication for those tunnels.
A common setup is:
Orca Mobile
-> authenticated tunnel edge
-> Cloudflare Tunnel / reverse proxy
-> Orca desktop/runtime
For example, Cloudflare Access can protect a tunnel with a service token. A non-interactive WebSocket client authenticates by sending:
CF-Access-Client-IdCF-Access-Client-Secret
during the WebSocket HTTP upgrade.
Today the direct mobile transport constructs the socket as:
new WebSocket(options.endpoint)so there is no way to attach credentials or other connection metadata required by an authenticated reverse proxy. An interactive Access/IdP page is not suitable for this path either.
The result is that users can put Orca behind a tunnel, but generally have to leave the tunnel endpoint reachable and rely on Orca's pairing/device authentication and E2EE alone.
Proposed solution
Add an authenticated custom endpoint option for Orca Mobile / direct remote connections.
A provider-neutral first version could support one of:
- Custom WebSocket handshake headers attached to the direct connection.
- A narrower service credential configuration that maps a stored key/value pair, or small set of headers, onto the WebSocket upgrade.
- A pluggable endpoint-auth abstraction if maintainers prefer not to expose arbitrary headers directly.
Important properties:
- Credentials should be stored using the platform's secure credential storage, not in pairing URLs.
- Pairing links / QR codes should never contain secret header values.
- Logs and diagnostics should redact configured credentials.
- Existing Orca device pairing, revocation, and E2EE should remain unchanged.
- The feature should not be Cloudflare-specific; Cloudflare Access service tokens are just a concrete motivating example.
- Existing LAN, Tailscale, and unauthenticated tunnel connections should continue to work unchanged.
Why this helps
It gives users a stronger BYO-tunnel option without requiring Orca Relay or a second VPN on mobile:
Cloudflare Access / authenticated reverse proxy
↓
Orca E2EE + device authentication
↓
Orca RPC
This keeps the external tunnel under the user's control while avoiding a publicly reachable unauthenticated WebSocket edge.
Related issues
- [Feature]: Add a first-class custom tunnel/VPN option for Orca Mobile #12535 — first-class custom tunnel/VPN option for Orca Mobile
- [Feature]: Add Cloudflare Tunnel as a pairing target for the browser access link #14039 — Cloudflare Tunnel as a pairing target
- [Bug]: Mobile custom network address / reverse-proxy remote access still fragile; web client Local PTYs + unavailableReason crash #9760 — custom network address / reverse-proxy remote access path
- Security: require E2EE v2 on direct mobile connections to prevent replay #17394 — require E2EE v2 on direct mobile connections to add replay protection
- [Feature]: Self-hosted relay server based mobile & desktop connections #2471 — self-hosted relay connections as an alternative architecture
This issue is intentionally narrower than those: it is about authenticating the existing direct/BYO tunnel path at the edge, not provisioning tunnels or replacing Orca's own pairing/E2EE.
Activity
chunchet-ng commentedon Oct 25, 2026
Related implementation is now split into focused PRs:
Orca pairing, pinned host identity and E2EE still apply after Access admits the connection. Credentials stay out of pairing links. Feedback on these contributions would be useful for this issue.
These are open review proposals, not released support. Upstream PR CI still needs maintainer approval; real-device and browser Access-session acceptance remain outstanding. Tunnel creation remains manual.