Skip to content

feat(auth): authenticate gateway-mediated application requests - #4963

Open
TaylorMutch wants to merge 8 commits into
feat/4953-authoritative-app-urls/TaylorMutchfrom
feat/4722-gateway-service-auth/TaylorMutch
Open

TaylorMutch wants to merge 8 commits into
feat/4953-authoritative-app-urls/TaylorMutchfrom
feat/4722-gateway-service-auth/TaylorMutch

Conversation

@TaylorMutch

@TaylorMutch TaylorMutch commented Oct 27, 2026 •

Copy link
Copy Markdown
Collaborator

Summary

Opt in to authentication and authorization for gateway-mediated application HTTP requests and WebSocket upgrades using service_auth_enabled = true in [openshell.gateway]. The default is false, preserving existing application routing. This setting is independent of the supervisor app listener and compute driver.

Based on main at bf9f55cdf. Stacked on feat/4953-authoritative-app-urls/TaylorMutch.

Related Issue

Closes #4722. Part of RFC 0017.

Changes

  • Log service authentication as enabled/disabled only when gateway-mediated service routing is enabled.

  • Apply service authentication and mount /auth/services only while gateway service routing is enabled. service_routing_enabled = false disables the gateway application path regardless of service_auth_enabled.

  • Add service_auth_enabled (default false), --service-auth-enabled true, OPENSHELL_SERVICE_AUTH_ENABLED=true, and Helm server.serviceAuthEnabled / canonical gatewayConfig."openshell.gateway".service_auth_enabled. Explicit false overrides are supported.

  • Preserve existing forwarding, application-owned paths, headers, and cookies when service authentication is disabled.

  • Store browser application-session tokens through the credential issuer using an explicit session owner, preserving existing backend scopes, opaque handles, and expiration checks.

  • Resolve browser login origins through the gateway route index for both readable and hashed service hosts, preserving workspace authorization and the control-plane login boundary.

  • Apply gateway identity, workspace access, and forwarding role/scope authorization before upstream connection.

  • Add browser login with single-use bootstrap codes and bounded Secure/HttpOnly/SameSite=Strict host-only sessions.

  • Use configured credential storage for sessions and shared revocation across gateway replicas.

  • Separate gateway credentials from application bearer tokens/cookies, strip reserved credentials, and enforce origin/Fetch Metadata protections.

Configuration

Configuration surface Enable gateway application authentication
Gateway TOML [openshell.gateway] → service_auth_enabled = true
Gateway CLI --service-auth-enabled=true
Environment OPENSHELL_SERVICE_AUTH_ENABLED=true
Canonical Helm values gatewayConfig."openshell.gateway".service_auth_enabled: true
Legacy Helm values server.serviceAuthEnabled: true

service_auth_enabled defaults to false. Precedence is CLI > environment > TOML > default; canonical Helm values override the legacy Helm setting.

[openshell.gateway]
service_routing_enabled = true
service_auth_enabled = true
Gateway routing Service auth Gateway application behavior
Enabled (default) Disabled (default) Existing forwarding without gateway application authentication
Enabled Enabled Require configured gateway authentication and workspace authorization
Disabled Either Return 404; do not mount /auth/services

These flags are independent of supervisor.app_listener.enabled. Direct app-listener access delegates authentication to the ingress provider/application.

Release Notes

Opt-in behavior change: enabling service_auth_enabled requires application clients to supply configured gateway authentication, with the app listener enabled or disabled. The default remains false. Direct app-listener authentication remains the ingress provider/application responsibility.

Compatibility

With service authentication disabled, configuring mTLS, operator auth, or OIDC preserves existing loopback HTTP URLs. Enabling service authentication selects HTTPS when gateway TLS is configured. Direct supervisor ingress strips only the two gateway service session/login cookies; other application cookies retain their behavior.

Testing

  • Startup logging: all eight app-listener/gateway-routing/service-auth combinations verified against the real gateway binary, with strict server Clippy and formatting checks. Full chart checks passed after correcting canonical routing/auth Helm examples and tests.

  • Gateway routing opt-out validation: 2,767 combined-stack server tests passed (43 PostgreSQL-dependent tests skipped), all nine proxy tests passed, and strict all-target server/proxy Clippy passed. Full Helm tests, Markdown lint, Rust formatting, and whitespace checks passed.

  • Previous validation on main e8ba30fde: standalone discovery passed 2,725 server tests (42 PostgreSQL-dependent tests skipped locally).

  • Combined stack passed 2,761 server tests (43 PostgreSQL-dependent tests skipped), nine proxy tests, and 19 supervisor listener regressions. Strict all-target server/supervisor/proxy Clippy passed.

  • TypeScript SDK validation passed: protobuf generation/lint, lint, type checking, 207 tests, coverage, and build.

  • Helm lint and all three chart unit suites passed, including gateway TOML parsing, resource coherence, ownership, and supervisor scaling checks. Markdown lint and Rust formatting passed.

  • Compatibility regressions cover recorded replay URLs across origin/port changes and disabled ingress, existing TypeScript object shapes, auth-disabled loopback schemes, application-cookie preservation, and real-TLS discovery-certificate opt-in behavior.

Earlier local k3d validation covered dedicated/shared owner changes, HTTP/WebSockets, network-policy isolation, discovery withdrawal, and two proxy replicas. This revision has no new live-cluster or production-load qualification. New-head CI is pending.

Qualification limits

Live HA validation exercised supervisor process/Pod loss on a local k3d cluster. Whole-node failure, real network partitions, metric-driven HPA, sustained production load, and published release artifacts remain unqualified. Grant-file projection contributes to revocation propagation time. Both ingress paths now share the gateway hostname format and label generator. The same installation identity and public HTTPS domain/port preserve service URLs when switching ingress. Installation-status presentation (#4670) remains separate work. Live Kubernetes runs above preceded hostname integration; the naming and shutdown-fence integration is validated by focused Rust regressions.

The example Kubernetes HTTPRoute controller is a deferred compatibility POC outside this stack.

Checklist

  • Follows Conventional Commits
  • Commits are signed off (DCO)
  • Relevant implementation, configuration, and API documentation updated

PR dependency order: #4956 → #4963 → #4964 → #4957.

Replaces #4959, which GitHub automatically marked merged into its former SDK base when the rebased branches were published. This draft isolates the auth change against the URL layer; main was unchanged by that event.

@copy-pr-bot

copy-pr-bot Bot commented Oct 27, 2026

Copy link
Copy Markdown

Auto-sync is disabled for draft pull requests in this repository. Workflows must be run manually.

Contributors can view more details about this message here.

@github-actions

Copy link
Copy Markdown

@TaylorMutch
TaylorMutch added this pull request to stack #4965 October 27, 2026 05:46
@TaylorMutch
TaylorMutch removed this pull request from stack #4965 October 27, 2026 05:47
@TaylorMutch
TaylorMutch force-pushed the feat/4722-gateway-service-auth/TaylorMutch branch from 18b394a to ce2a99e Compare October 27, 2026 06:24
@TaylorMutch
TaylorMutch force-pushed the feat/4953-authoritative-app-urls/TaylorMutch branch from 2574b9a to 70e365e Compare October 27, 2026 06:24
@TaylorMutch
TaylorMutch force-pushed the feat/4722-gateway-service-auth/TaylorMutch branch from ce2a99e to de94456 Compare October 27, 2026 06:25
@TaylorMutch
TaylorMutch force-pushed the feat/4953-authoritative-app-urls/TaylorMutch branch 2 times, most recently from 30cf9ce to 6b2fe9c Compare October 27, 2026 06:46
@TaylorMutch
TaylorMutch force-pushed the feat/4722-gateway-service-auth/TaylorMutch branch from de94456 to 3b08d4c Compare October 27, 2026 06:46
@TaylorMutch
TaylorMutch force-pushed the feat/4953-authoritative-app-urls/TaylorMutch branch from 6b2fe9c to dae4a9d Compare October 27, 2026 21:06
@TaylorMutch
TaylorMutch force-pushed the feat/4722-gateway-service-auth/TaylorMutch branch 2 times, most recently from c35e581 to caacd27 Compare October 28, 2026 17:05
@TaylorMutch
TaylorMutch force-pushed the feat/4953-authoritative-app-urls/TaylorMutch branch 2 times, most recently from 66220a7 to 3dc01d7 Compare October 28, 2026 22:52
@TaylorMutch
TaylorMutch force-pushed the feat/4722-gateway-service-auth/TaylorMutch branch 3 times, most recently from c37b455 to dd566cd Compare October 30, 2026 17:57
@TaylorMutch
TaylorMutch force-pushed the feat/4953-authoritative-app-urls/TaylorMutch branch 2 times, most recently from b71991c to ad8be4d Compare October 30, 2026 18:13
@TaylorMutch
TaylorMutch force-pushed the feat/4722-gateway-service-auth/TaylorMutch branch 2 times, most recently from 00061b6 to acc3754 Compare October 30, 2026 21:11
@TaylorMutch
TaylorMutch force-pushed the feat/4722-gateway-service-auth/TaylorMutch branch 2 times, most recently from 2273f0d to 75d3340 Compare November 10, 2026 08:41
@TaylorMutch
TaylorMutch force-pushed the feat/4953-authoritative-app-urls/TaylorMutch branch from 2c15db3 to 15f0afb Compare November 10, 2026 08:41
@TaylorMutch
TaylorMutch force-pushed the feat/4722-gateway-service-auth/TaylorMutch branch from 75d3340 to 7224961 Compare November 12, 2026 20:17
@TaylorMutch
TaylorMutch force-pushed the feat/4953-authoritative-app-urls/TaylorMutch branch from 15f0afb to 6903eaa Compare November 12, 2026 20:17
@TaylorMutch
TaylorMutch force-pushed the feat/4722-gateway-service-auth/TaylorMutch branch from 7224961 to 5f66489 Compare November 13, 2026 21:15
@TaylorMutch
TaylorMutch force-pushed the feat/4953-authoritative-app-urls/TaylorMutch branch from 6903eaa to 433b9b9 Compare November 13, 2026 21:15
@purp purp added area:enterprise Authentication, multitenancy, gateway interceptors, FIPS, and enterprise requirements. topic:authnz Authentication, authorization, identity, sessions, credential protection, and policy integrity. topic:documentation Architecture docs, READMEs, project website updates, and automated documentation generation. topic:operability Installing/configuring deployments, upgrades, backup/restore, diagnostics, and maintenance. topic:security Vulnerability management, security analysis/auditing, bypass detection, and abuse prevention. labels Nov 15, 2026
@TaylorMutch
TaylorMutch marked this pull request as ready for review November 16, 2026 19:22
@github-actions

Copy link
Copy Markdown

Compatibility review (advisory)

New or updated breaking changes; see the full report for all findings.

1. api-behavior — No explicit risk acceptance found

TLS loopback gateways now advertise https:// instead of http:// when mTLS, operator authentication, or OIDC is configured, even with service_auth_enabled=false.

  • Impact: Browsers and SDK consumers following returned service URLs can fail certificate validation or lose HTTP-origin state despite unchanged configuration.
  • Action: For v0.1.9, preserve HTTP advertisement when service authentication is disabled and reserve the HTTPS switch for explicit opt-in with TLS-trust and origin-migration guidance.
  • PR: feat(auth): authenticate gateway-mediated application requests #4963

2. api-behavior — No explicit risk acceptance found

The supervisor application listener now drops every __Host-openshell-* request cookie instead of filtering only Cloudflare authentication cookies.

  • Impact: Applications using previously forwarded cookies such as __Host-openshell-app lose session state through direct supervisor ingress even with service_auth_enabled=false.
  • Action: Preserve existing application-cookie forwarding in v0.1.9 and make any new reserved-cookie filtering explicitly opt-in with documented cookie-renaming guidance.
  • PR: feat(auth): authenticate gateway-mediated application requests #4963
Review details
  • Execution: complete
  • Candidate: PR #4963 (6bb8b3d1e00438f877d8c2ed5a80ded30144903c)
  • Baseline: 433b9b936ed7e6e63a8d359cfbdad4fb41ebb0d8 (433b9b936ed7e6e63a8d359cfbdad4fb41ebb0d8)
  • Reviewed: rust-sdk, python-sdk, typescript-sdk, api-behavior, cli, configuration, policy, helm, state

Advisory review; publication gates are unchanged.

Branch check run

@TaylorMutch
TaylorMutch force-pushed the feat/4953-authoritative-app-urls/TaylorMutch branch from 433b9b9 to 35e2d05 Compare November 16, 2026 19:55
@TaylorMutch
TaylorMutch force-pushed the feat/4722-gateway-service-auth/TaylorMutch branch from 5f66489 to 2bc4518 Compare November 16, 2026 19:55
@github-actions

Copy link
Copy Markdown

Compatibility review (advisory)

New or updated breaking changes; see the full report for all findings.

1. helm — No explicit risk acceptance found

helm upgrade --reuse-values previously accepted saved chart values but now renders service_auth_enabled = "" when the new server.serviceAuthEnabled key is absent.

  • Impact: Existing installations upgraded with --reuse-values receive invalid gateway TOML, preventing replacement gateway pods from starting even without opting into service authentication.
  • Action: For v0.1.9, default an absent server.serviceAuthEnabled to boolean false; document --set server.serviceAuthEnabled=false as an interim upgrade workaround.
  • PR: feat(auth): authenticate gateway-mediated application requests #4963
Review details
  • Execution: complete
  • Candidate: PR #4963 (a1c3d4ff983098356da4f251cf19071db98e1785)
  • Baseline: 35e2d054e2a1194e53695e449974ea34a4d5a71f (35e2d054e2a1194e53695e449974ea34a4d5a71f)
  • Reviewed: rust-sdk, python-sdk, typescript-sdk, api-behavior, cli, configuration, policy, helm, state

Advisory review; publication gates are unchanged.

Branch check run

@TaylorMutch
TaylorMutch force-pushed the feat/4722-gateway-service-auth/TaylorMutch branch from 2bc4518 to f79878c Compare November 16, 2026 21:48
@TaylorMutch
TaylorMutch force-pushed the feat/4953-authoritative-app-urls/TaylorMutch branch from 35e2d05 to c503a94 Compare November 16, 2026 21:48
@TaylorMutch
TaylorMutch force-pushed the feat/4722-gateway-service-auth/TaylorMutch branch 2 times, most recently from 0b04cc3 to c0123e1 Compare November 17, 2026 00:48
Require configured gateway authentication for application HTTP requests
and WebSocket upgrades, with or without the independent app listener.
Add browser sessions, application credential separation, shared revocation,
request authorization, documentation, and browser coverage.

Closes #4722

Signed-off-by: Taylor Mutch <taylormutch@gmail.com>
Signed-off-by: Taylor Mutch <taylormutch@gmail.com>
Signed-off-by: Taylor Mutch <taylormutch@gmail.com>
Signed-off-by: Taylor Mutch <taylormutch@gmail.com>
Signed-off-by: Taylor Mutch <taylormutch@gmail.com>
Signed-off-by: Taylor Mutch <taylormutch@gmail.com>
Signed-off-by: Taylor Mutch <taylormutch@gmail.com>
Signed-off-by: Taylor Mutch <taylormutch@gmail.com>
@TaylorMutch
TaylorMutch force-pushed the feat/4722-gateway-service-auth/TaylorMutch branch from c0123e1 to e5927f4 Compare November 17, 2026 23:14

This branch has not been deployed

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

Labels

area:enterprise Authentication, multitenancy, gateway interceptors, FIPS, and enterprise requirements. topic:authnz Authentication, authorization, identity, sessions, credential protection, and policy integrity. topic:documentation Architecture docs, READMEs, project website updates, and automated documentation generation. topic:operability Installing/configuring deployments, upgrades, backup/restore, diagnostics, and maintenance. topic:security Vulnerability management, security analysis/auditing, bypass detection, and abuse prevention.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants