Skip to content

fix: Point forwarding headers at the external Trino endpoint - #119

Open
sbernauer wants to merge 1 commit into
mainfrom
fix/forwarded-headers
Open

fix: Point forwarding headers at the external Trino endpoint#119
sbernauer wants to merge 1 commit into
mainfrom
fix/forwarded-headers

Conversation

@sbernauer

@sbernauer sbernauer commented Jul 30, 2026

Copy link
Copy Markdown
Member

Fixes SUP-386

Trino builds the absolute URLs it hands out to clients (OAuth 2.0 challenge, infoUri, ackUri) from the forwarding headers. These pointed at trino-lb, so clients got sent to /oauth2/token/{id} on trino-lb, which answers with a 404 and breaks the whole authentication flow.

Trino builds the absolute URLs it hands out to clients (OAuth 2.0
challenge, infoUri, ackUri) from the forwarding headers. These pointed
at trino-lb, so clients got sent to /oauth2/token/{id} on trino-lb,
which answers with a 404 and breaks the whole authentication flow.
@sbernauer sbernauer self-assigned this Jul 31, 2026
@sbernauer sbernauer moved this to Development: Waiting for Review in Stackable Engineering Jul 31, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

Status: Development: Waiting for Review

Development

Successfully merging this pull request may close these issues.

2 participants