You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Dec 7, 2020. It is now read-only.
Some Applications need a very specific Header-Format. As far I i see, all custom-headers are prefixed with X-Auth-. Although this is fine for most cases, it obstructs most migration/legacy scenarios.
Extending the configuration to make the header-prefix modifiable or simply switch from a list-style config to mappings ({{Some-Claim: some_claim => X-Some-Claim: some_claim content}}) would be sufficent.
What:
Some Applications need a very specific Header-Format. As far I i see, all custom-headers are prefixed with
X-Auth-
. Although this is fine for most cases, it obstructs most migration/legacy scenarios.Extending the configuration to make the header-prefix modifiable or simply switch from a list-style config to mappings ({{Some-Claim: some_claim => X-Some-Claim: some_claim content}}) would be sufficent.
Reference:
The text was updated successfully, but these errors were encountered: