public_git
/
oauth2-proxy
mirror of https://github.com/oauth2-proxy/oauth2-proxy.git
1
0
Fork 0
Code Issues Projects Releases Wiki Activity

Merge 9963d7da0c into 1f049e5ebd

This commit is contained in:
nightcityblade 2026-08-12 19:17:49 +02:00 committed by GitHub
parent 1f049e5ebd 9963d7da0c
commit 35df297942
No known key found for this signature in database
GPG Key ID: B5690EEEBB952194
2 changed files with 22 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

11
docs/docs/configuration/alpha_config.md
View File

@ -167,6 +167,17 @@ injectResponseHeaders:
* `claimSource` - `claim` (session claims either from id token or from profile URL)
* `secretSource` - `value` (base64), `fromFile` (file path)
#### Claim value serialization
`claimSource` converts the selected claim into one or more string header values. Scalars
produce one value, while arrays produce one value per element. Values that cannot be
converted directly to strings, such as objects, are JSON-encoded individually.
Each non-empty value is added separately under the configured header name. An array of
objects therefore produces multiple header values containing one JSON object each, not a
single JSON array. HTTP libraries and intermediaries may expose repeated values as a
comma-joined string, so consumers should retrieve and parse each header value separately.
**Request option:** `preserveRequestValue: true` retains existing header values
**Incompatibility:** Remove legacy flags `pass-user-headers`, `set-xauthrequest`

11
docs/docs/configuration/alpha_config.md.tmpl
View File

@ -167,6 +167,17 @@ injectResponseHeaders:
* `claimSource` - `claim` (session claims either from id token or from profile URL)
* `secretSource` - `value` (base64), `fromFile` (file path)
#### Claim value serialization
`claimSource` converts the selected claim into one or more string header values. Scalars
produce one value, while arrays produce one value per element. Values that cannot be
converted directly to strings, such as objects, are JSON-encoded individually.
Each non-empty value is added separately under the configured header name. An array of
objects therefore produces multiple header values containing one JSON object each, not a
single JSON array. HTTP libraries and intermediaries may expose repeated values as a
comma-joined string, so consumers should retrieve and parse each header value separately.
**Request option:** `preserveRequestValue: true` retains existing header values
**Incompatibility:** Remove legacy flags `pass-user-headers`, `set-xauthrequest`