Skip to content

bridges: strip client Authorization at the Route - #44

Merged
guygrigsby merged 1 commit into
mainfrom
guy/bridge-route-strip-authorization
Sep 22, 2026
Merged

guygrigsby merged 1 commit into
mainfrom
guy/bridge-route-strip-authorization

Conversation

@guygrigsby

@guygrigsby guygrigsby commented Sep 22, 2026 •

Copy link
Copy Markdown
Contributor

Drops the Authorization header in the Route's proxy director before a request leaves for Aperture.

Every client launched sends a placeholder bearer (not-needed, -, whatever its SDK accepts) because the SDK refuses to build a request without one. Ingress auth at Aperture is the machine's tailnet identity, so the header is never actually used. A gateway that treats it as authoritative rejects it with a 401. Stripping it once at the Route fixes every client at the same time rather than hunting for a placeholder each gateway tolerates.

Every client aperture-cli launches sends a placeholder bearer because
its SDK refuses to build a request without one. A gateway that treats
the header as authoritative rejects it with a 401, which is the Solar
Winds failure. Ingress auth at the Aperture is the Machine's tailnet
identity and every upstream auth mode either replaces or strips the
client header, so dropping it at the Route is safe and fixes all
clients at once.
@guygrigsby
guygrigsby merged commit 1717497 into main Sep 22, 2026
2 checks passed
@guygrigsby
guygrigsby deleted the guy/bridge-route-strip-authorization branch September 22, 2026 15:53
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant