Skip to content

fix(docs): avoid conflicting Istio auth headers - #132

Open
pushpinderbal wants to merge 1 commit into
tinyauthapp:mainfrom
pushpinderbal:fix/istio-auth-header-conflict
Open

fix(docs): avoid conflicting Istio auth headers#132
pushpinderbal wants to merge 1 commit into
tinyauthapp:mainfrom
pushpinderbal:fix/istio-auth-header-conflict

Conversation

@pushpinderbal

@pushpinderbal pushpinderbal commented Sep 9, 2026

Copy link
Copy Markdown
Contributor

Updates the Istio/Kubernetes ext_authz examples to use the minimal required request headers and removes unnecessary additional-header overrides, aligning the documentation with tinyauth#1089.

@coderabbitai

coderabbitai Bot commented Sep 9, 2026

Copy link
Copy Markdown
Contributor

Important

  • 🔍 Trigger review

This repository does not receive automatic reviews because it has fewer than 10 stars.

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Advanced

Run ID: 6b14b05b-5a0a-4cf1-8764-48540139d017


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

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

@pushpinderbal
pushpinderbal marked this pull request as draft September 9, 2026 03:04
Co-Authored-By: Codex <codex@users.noreply.github.com>
@pushpinderbal
pushpinderbal force-pushed the fix/istio-auth-header-conflict branch from e128e14 to 7f678ce Compare September 9, 2026 04:29
@pushpinderbal
pushpinderbal marked this pull request as ready for review September 9, 2026 04:32
Comment on lines -82 to -86
includeRequestHeadersInCheck: ["cookie", "x-forwarded-for", "x-forwarded-proto", "x-forwarded-host", "accept", "user-agent"]
includeAdditionalHeadersInCheck:
"x-forwarded-for": "%DOWNSTREAM_REMOTE_ADDRESS_WITHOUT_PORT%"
"x-real-ip": "%DOWNSTREAM_REMOTE_ADDRESS_WITHOUT_PORT%"
"x-forwarded-proto": "%REQ(:SCHEME)%"

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I would keep all headers except the x-forwarded-uri and x-forwarded-host. The real IP, the forwarded for and the original proto/method are good to have (the proto is required by the ext_authz module as well).

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

"x-forwarded-for", "x-forwarded-proto" are still included in includeRequestHeadersInCheck, we don't necessarily need to copy the same in includeAdditionalHeadersInCheck as the connection manager by default sanitizes/determines these headers (unless we want to override the default value Envoy determines).
Will add x-real-ip in includeAdditionalHeadersInCheck, and accept back.

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Basically the headers we need are:

x-forwarded-for
x-real-ip
x-forwarded-proto

And we should be good to go. You are the envoy expert so :)

Comment on lines -114 to -121
includeRequestHeadersInCheck: ["cookie", "x-forwarded-for", "x-forwarded-proto", "x-forwarded-host", "accept", "user-agent"]
includeAdditionalHeadersInCheck:
"x-forwarded-for": "%DOWNSTREAM_REMOTE_ADDRESS_WITHOUT_PORT%"
"x-real-ip": "%DOWNSTREAM_REMOTE_ADDRESS_WITHOUT_PORT%"
"x-forwarded-proto": "%REQ(:SCHEME)%"
"x-forwarded-host": "%REQ(:AUTHORITY)%"
"x-forwarded-uri": "%REQ(:PATH)%"
"x-forwarded-method": "%REQ(:METHOD)%"

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

See the comment above.

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.

2 participants