Set Authorization Header
Summary
caution
As of v0.23.0, set_authorization_header has been deprecated in favor of set_request_headers and will be removed in v0.24.0.
Now, set_request_headers allows you to include ID and Access tokens in requests so you don't have to designate the Authorization header to send these values.
Set Authorization Header allows you to send a user's identity token through as a bearer token in the Authorization header.
How to configure
- Core
- Enterprise
- Kubernetes
| YAML/JSON setting | Type | Default | Usage |
|---|---|---|---|
set_authorization_header | string | pass_through | optional |
Configure Set Authorization Header in the Console:
Kubernetes does not support Set Authorization Header
Options
| Option | Definition |
|---|---|
access_token | Send the OAuth access token |
id_token | Send the OIDC ID token |
pass_through | Leave the Authorization header unchanged from the client when it's not used for Pomerium authentication |
Examples
set_authorization_header: pass_through