Project: OAuth2 Proxy (Provisioning / Key Management)
File: overview.md

id: overview title: Overview `oauth2-proxy` can be configured via , or (in decreasing order of precedence, i.e. command line options will overwrite environment variables and environment variables will overwrite configuration file settings). To generate a strong cookie secret use one of the below commands: import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; <Tabs defaultValue="python" values={[ {label: 'Python', value: 'python'}, {label: 'Bash', value: 'bash'}, {label: 'OpenSSL', value: 'openssl'}, {label: 'PowerShell', value: 'powershell'}, {label: 'Terraform', value: 'terraform'}, ]}> <TabItem value="python"> ```shell python -c 'import os,base64; print(base64.urlsafe_b64encode(os.urandom(32)).decode())' ``` </TabItem> <TabItem value="bash"> ```shell dd if=/dev/urandom bs=32 count=1 2>/dev/null | base64 | tr -d -- '\n' | tr -- '+/' '-_'; echo ``` </TabItem> <TabItem value="openssl"> ```shell openssl rand -base64 32 | tr -- '+/' '-_' ``` </TabItem> <TabItem value="powershell"> ```shell Add-Type -AssemblyName System.Web ``` </TabItem> <TabItem value="terraform"> ```shell resource "randompassword" "cookiesecret" { length = 32 overridespecial = "-" } ``` </TabItem> </Tabs> Every command line argument can be specified in a config file by replacing hyphens (-) with underscores (\_). If the argument can be specified multiple times, the config option should be plural (trailing s). An example config file is in the contrib directory. It can be used by specifying `--config=/etc/oauth2-proxy.cfg` | Option | Type | Description | Default | | - | -- | | | | `--acr-values` | string | optional, see | `""` | | `--api-route` | string \| list | return HTTP 401 instead of redirecting to authentication server if token is not valid. Format: path_regex | | | `--approval-prompt` | string | OAuth approval_prompt | `"force"` | | `--auth-logging` | bool | Log authentication attempts | true | | `--auth-logging-format` | string | Template for authentication log lines | see | | `--authenticated-emails-file` | string | authenticate against emails via file (one per line) | | | `--azure-tenant` | string | go to a tenant-specific or common (tenant-independent) endpoint. | `"common"` | | `--basic-auth-password` | string | the password to set when passing the HTTP Basic Auth header | | | `--client-id` | string | the OAuth Client ID, e.g. `"123456.apps.googleusercontent.com"` | | | `--client-secret` | string | the OAuth Client Secret | | | `--client-secret-file` | string | the file with OAuth Client Secret | | | `--code-challenge-method` | string | use PKCE code challenges with the specified method. Either 'plain' or 'S256' (recommended) | | | `--config` | string | path to config file | | | `--cookie-domain` | string \| list | Optional cookie domains to force cookies to (e.g. `.yourcompany.com`). The longest domain matching the request's host will be used (or the shortest cookie domain if there is no match). | | | `--cookie-expire` | duration | expire timeframe for cookie. If set to 0, cookie becomes a session-cookie which will expire when the browser is closed. | 168h0m0s | | `--cookie-httponly` | bool | set HttpOnly cookie flag | true | | `--cookie-name` | string | the name of the cookie that the oauthproxy creates. Should be changed to use a (`Host-` or `Secure-`) if `--cookie-secure` is set. | `"oauth2_proxy"` | | `--cookie-path` | string | an optional cookie path to force cookies to

`/poc/`) | `"/"` | | `--cookie-refresh` | duration | refresh the cookie after this duration; `0` to disable; not supported by all providers&nbsp;[^1] | | | `--cookie-secret` | string | the seed string for secure cookies (optionally base64 encoded) | | | `--cookie-secure` | bool | set | true | | `--cookie-samesite` | string | set SameSite cookie attribute (`"lax"`, `"strict"`, `"none"`, or `""`). | `""` | | `--cookie-csrf-per-request` | bool | Enable having different CSRF cookies per request, making it possible to have parallel requests. | false | | `--cookie-csrf-expire` | duration | expire timeframe for CSRF cookie | 15m | | `--custom-templates-dir` | string | path to custom html templates | | | `--custom-sign-in-logo` | string | path or a URL to an custom image for the sign_in page logo. Use `"-"` to disable default logo. | | `--display-htpasswd-form` | bool | display username / password login form if an htpasswd file is provided | true | | `--email-domain` | string \| list | authenticate emails with the specified domain (may be given multiple times). Use `*` to authenticate any email | | | `--errors-to-info-log` | bool | redirects error-level logging to default log channel instead of stderr | false | | `--extra-jwt-issuers` | string | if `--skip-jwt-bearer-tokens` is set, a list of extra JWT `issuer=audience` (see a token's `iss`, `aud` fields) pairs (where the issuer URL has a `.well-known/openid-configuration` or a `.well-known/jwks.json`) | | | `--exclude-logging-path` | string | comma separated list of paths to exclude from logging, e.g. `"/ping,/path2"` | `""` (no paths excluded) | | `--flush-interval` | duration | period between flushing response buffers when streaming responses | `"1s"` | | `--force-https` | bool | enforce https redirect | `false` | | `--force-json-errors` | bool | force JSON errors instead of HTTP error pages or redirects | `false` | | `--banner` | string | custom (html) banner string. Use `"-"` to disable default banner. | | | `--footer` | string | custom (html) footer string. Use `"-"` to disable default footer. | | | `--github-org` | string | restrict logins to members of this organisation | | | `--github-team` | string | restrict logins to members of any of these teams (slug), separated by a comma | | | `--github-repo` | string | restrict logins to collaborators of this repository formatted as `orgname/repo` | | | `--github-token` | string | the token to use when verifying repository collaborators (must have push access to the repository) | | | `--github-user` | string \| list | To allow users to login by username even if they do not belong to the specified org and team or collaborators | | | `--gitlab-group` | string \| list | restrict logins to members of any of these groups (slug), separated by a comma | | | `--gitlab-projects` | string \| list | restrict logins to members of any of these projects (may be given multiple times) formatted as `orgname/repo=accesslevel`. Access level should be a value matching , defaulted to 20 if absent | | | `--google-admin-email` | string | the google admin to impersonate for api calls | | | `--google-group` | string | restrict logins to members of this google group (may be given multiple times). | | | `--google-service-account-json` | string | the path to the service account json credentials | | | `--google-use-application-default-credentials` | bool | use application default credentials instead of service account json (i.e. GKE Workload Identity) | | | `--htpasswd-file` | string | additionally authenticate against a htpasswd file. Entries must be created with `htpasswd -B` for bcrypt encryption | | | `--htpasswd-user-group` | string \| list | the groups to be set on sessions for htpasswd users | | | `--http-address` | string | `[http://]<addr>:<port>` or `unix://<path>` to listen on for HTTP clients. Square brackets are required for ipv6 address, e.g. `http://[::1]:4180` |

| | `--https-address` | string | `[https://]<addr>:<port>` to listen on for HTTPS clients. Square brackets are required for ipv6 address, e.g. `https://[::1]:443` | `":443"` | | `--logging-compress` | bool | Should rotated log files be compressed using gzip | false | | `--logging-filename` | string | File to log requests to, empty for `stdout` | `""` (stdout) | | `--logging-local-time` | bool | Use local time in log files and backup filenames instead of UTC | true (local time) | | `--logging-max-age` | int | Maximum number of days to retain old log files | 7 | | `--logging-max-backups` | int | Maximum number of old log files to retain; 0 to disable | 0 | | `--logging-max-size` | int | Maximum size in megabytes of the log file before rotation | 100 | | `--jwt-key` | string | private key in PEM format used to sign JWT, so that you can say something like `--jwt-key="${OAUTH2PROXYJWT_KEY}"`: required by login.gov | | | `--jwt-key-file` | string | path to the private key file in PEM format used to sign the JWT so that you can say something like `--jwt-key-file=/etc/ssl/private/jwtsigningkey.pem`: required by login.gov | | | `--login-url` | string | Authentication endpoint | | | `--insecure-oidc-allow-unverified-email` | bool | don't fail if an email address in an id_token is not verified | false | | `--insecure-oidc-skip-issuer-verification` | bool | allow the OIDC issuer URL to differ from the expected (currently required for Azure multi-tenant compatibility) | false | | `--insecure-oidc-skip-nonce` | bool | skip verifying the OIDC ID Token's nonce claim | true | | `--oidc-issuer-url` | string | the OpenID Connect issuer URL, e.g. `"https://accounts.google.com"` | | | `--oidc-jwks-url` | string | OIDC JWKS URI for token verification; required if OIDC discovery is disabled | | | `--oidc-email-claim` | string | which OIDC claim contains the user's email | `"email"` | | `--oidc-groups-claim` | string | which OIDC claim contains the user groups | `"groups"` | | `--oidc-audience-claim` | string | which OIDC claim contains the audience | `"aud"` | | `--oidc-extra-audience` | string \| list | additional audiences which are allowed to pass verification | `"[]"` | | `--pass-access-token` | bool | pass OAuth access_token to upstream via X-Forwarded-Access-Token header. When used with `--set-xauthrequest` this adds the X-Auth-Request-Access-Token header to the response | false | | `--pass-authorization-header` | bool | pass OIDC IDToken to upstream via Authorization Bearer header | false | | `--pass-basic-auth` | bool | pass HTTP Basic Auth, X-Forwarded-User, X-Forwarded-Email and X-Forwarded-Preferred-Username information to upstream | true | | `--prefer-email-to-user` | bool | Prefer to use the Email address as the Username when passing information to upstream. Will only use Username if Email is unavailable, e.g. htaccess authentication. Used in conjunction with `--pass-basic-auth` and `--pass-user-headers` | false | | `--pass-host-header` | bool | pass the request Host Header to upstream | true | | `--pass-user-headers` | bool | pass X-Forwarded-User, X-Forwarded-Groups, X-Forwarded-Email and X-Forwarded-Preferred-Username information to upstream | true | | `--profile-url` | string | Profile access endpoint | | | `--prompt` | string | ; if present, `approval-prompt` is ignored | `""` | | `--provider` | string | OAuth provider | google | | `--provider-ca-file` | string \| list | Paths to CA certificates that should be used when connecting to the provider. If not specified, the default Go trust sources are used

| | `--provider-display-name` | string | Override the provider's name with the given string; used for the sign-in page | (depends on provider) | | `--ping-path` | string | the ping endpoint that can be used for basic health checks | `"/ping"` | | `--ping-user-agent` | string | a User-Agent that can be used for basic health checks | `""` (don't check user agent) | | `--ready-path` | string | the ready endpoint that can be used for deep health checks | `"/ready"` | | `--metrics-address` | string | the address prometheus metrics will be scraped from | `""` | | `--proxy-prefix` | string | the url root path that this proxy should be nested under (e.g. /`<oauth2>/sign_in`) | `"/oauth2"` | | `--proxy-websockets` | bool | enables WebSocket proxying | true | | `--pubjwk-url` | string | JWK pubkey access endpoint: required by login.gov | | | `--real-client-ip-header` | string | Header used to determine the real IP of the client, requires `--reverse-proxy` to be set (one of: X-Forwarded-For, X-Real-IP, or X-ProxyUser-IP) | X-Real-IP | | `--redeem-url` | string | Token redemption endpoint | | | `--redirect-url` | string | the OAuth Redirect URL, e.g. `"https://internalapp.yourcompany.com/oauth2/callback"` | | | `--redis-cluster-connection-urls` | string \| list | List of Redis cluster connection URLs (e.g. `redis://HOST[:PORT]`). Used in conjunction with `--redis-use-cluster` | | | `--redis-connection-url` | string | URL of redis server for redis session storage (e.g. `redis://HOST[:PORT]`) | | | `--redis-insecure-skip-tls-verify` | bool | skip TLS verification when connecting to Redis | false | | `--redis-password` | string | Redis password. Applicable for all Redis configurations. Will override any password set in `--redis-connection-url` | | | `--redis-sentinel-password` | string | Redis sentinel password. Used only for sentinel connection; any redis node passwords need to use `--redis-password` | | | `--redis-sentinel-master-name` | string | Redis sentinel master name. Used in conjunction with `--redis-use-sentinel` | | | `--redis-sentinel-connection-urls` | string \| list | List of Redis sentinel connection URLs (e.g. `redis://HOST[:PORT]`). Used in conjunction with `--redis-use-sentinel` | | | `--redis-use-cluster` | bool | Connect to redis cluster. Must set `--redis-cluster-connection-urls` to use this feature | false | | `--redis-use-sentinel` | bool | Connect to redis via sentinels. Must set `--redis-sentinel-master-name` and `--redis-sentinel-connection-urls` to use this feature | false | | `--redis-connection-idle-timeout` | int | Redis connection idle timeout seconds. If Redis option is set to non-zero, the `--redis-connection-idle-timeout` must be less than Redis timeout option. Exmpale: if either redis.conf includes `timeout 15` or using `CONFIG SET timeout 15` the `--redis-connection-idle-timeout` must be at least `--redis-connection-idle-timeout=14` | 0 | | `--request-id-header` | string | Request header to use as the request ID in logging | X-Request-Id | | `--request-logging` | bool | Log requests | true | | `--request-logging-format` | string | Template for request log lines | see | | `--resource` | string | The resource that is protected (Azure AD only) | | | `--reverse-proxy` | bool | are we running behind a reverse proxy, controls whether headers like X-Real-IP are accepted and allows X-Forwarded-\{Proto,Host,Uri\} headers to be used on redirect selection | false | | `--scope` | string | OAuth scope specification | | | `--session-cookie-minimal` | bool | strip OAuth tokens from cookie session stores if they aren't needed (cookie session store only) | false | | `--session-store-type` | string | ; redis or cookie | cookie | | `--set-xauthrequest` | bool | set X-Auth-Request-User, X-Auth-Request-Groups, X-Auth-Request-Email and X-Auth-Request-Preferred-Username response headers (useful in Nginx auth_request mode). When used with `--pass-access-token`, X-Auth-Request-Access-Token is added to response

| false | | `--set-authorization-header` | bool | set Authorization Bearer response header (useful in Nginx auth_request mode) | false | | `--set-basic-auth` | bool | set HTTP Basic Auth information in response (useful in Nginx auth_request mode) | false | | `--show-debug-on-error` | bool | show detailed error information on error pages (WARNING: this may contain sensitive information - do not use in production) | false | | `--signature-key` | string | GAP-Signature request signature key (algorithm:secretkey) | | | `--silence-ping-logging` | bool | disable logging of requests to ping & ready endpoints | false | | `--skip-auth-preflight` | bool | will skip authentication for OPTIONS requests | false | | `--skip-auth-regex` | string \| list | (DEPRECATED for `--skip-auth-route`) bypass authentication for requests paths that match (may be given multiple times) | | | `--skip-auth-route` | string \| list | bypass authentication for requests that match the method & path. Format: method=pathregex OR method!=pathregex. For all methods: pathregex OR !=pathregex | | | `--skip-auth-strip-headers` | bool | strips `X-Forwarded-*` style authentication headers & `Authorization` header if they would be set by oauth2-proxy | true | | `--skip-jwt-bearer-tokens` | bool | will skip requests that have verified JWT bearer tokens (the token must have that matches this client id or one of the extras from `extra-jwt-issuers`) | false | | `--skip-oidc-discovery` | bool | bypass OIDC endpoint discovery. `--login-url`, `--redeem-url` and `--oidc-jwks-url` must be configured in this case | false | | `--skip-provider-button` | bool | will skip sign-in-page to directly reach the next step: oauth/start | false | | `--ssl-insecure-skip-verify` | bool | skip validation of certificates presented when using HTTPS providers | false | | `--ssl-upstream-insecure-skip-verify` | bool | skip validation of certificates presented when using HTTPS upstreams | false | | `--standard-logging` | bool | Log standard runtime information | true | | `--standard-logging-format` | string | Template for standard log lines | see | | `--tls-cert-file` | string | path to certificate file | | | `--tls-cipher-suite` | string \| list | Restricts TLS cipher suites used by server to those listed (e.g. TLSRSAWITHRC4128_SHA) (may be given multiple times). If not specified, the default Go safe cipher list is used. List of valid cipher suites can be found in the . | | | `--tls-key-file` | string | path to private key file | | | `--tls-min-version` | string | minimum TLS version that is acceptable, either `"TLS1.2"` or `"TLS1.3"` | `"TLS1.2"` | | `--upstream` | string \| list | the http url(s) of the upstream endpoint, file:// paths for static files or `static://<status_code>` for static response. Routing is based on the path | | | `--upstream-timeout` | duration | maximum amount of time the server will wait for a response from the upstream | 30s | | `--allowed-group` | string \| list | restrict logins to members of this group (may be given multiple times) | | | `--allowed-role` | string \| list | restrict logins to users with this role (may be given multiple times). Only works with the keycloak-oidc provider. | | | `--validate-url` | string | Access token validation endpoint | | | `--version` | n/a | print version string | | | `--whitelist-domain` | string \| list | allowed domains for redirection after authentication. Prefix domain with a `.` or a `.` to allow subdomains (e.g. `.example.com`, `.example.com`)&nbsp;[^2] | | | `--trusted-ip` | string \| list | list of IPs or CIDR ranges to allow to bypass authentication (may be given multiple

When combined with `--reverse-proxy` and optionally `--real-client-ip-header` this will evaluate the trust of the IP stored in an HTTP header by a reverse proxy rather than the layer-3/4 remote address. WARNING: trusting IPs has inherent security flaws, especially when obtaining the IP address from an HTTP header (reverse-proxy mode). Use this option only if you understand the risks and how to manage them. | | See below for provider specific options `oauth2-proxy` supports having multiple upstreams, and has the option to pass requests on to HTTP(S) servers or serve static files from the file system. HTTP and HTTPS upstreams are configured by providing a URL such as `http://127.0.0.1:8080/` for the upstream parameter. This will forward all authenticated requests to the upstream server. If you instead provide `http://127.0.0.1:8080/some/path/` then it will only be requests that start with `/some/path/` which are forwarded to the upstream. Static file paths are configured as a file:// URL. `file:///var/www/static/` will serve the files from that directory at `http://[oauth2-proxy url]/var/www/static/`, which may not be what you want. You can provide the path to where the files should be available by adding a fragment to the configured URL. The value of the fragment will then be used to specify which path the files are available at, e.g. `file:///var/www/static/#/static/` will make `/var/www/static/` available at `http://[oauth2-proxy url]/static/`. Multiple upstreams can either be configured by supplying a comma separated list to the `--upstream` parameter, supplying the parameter multiple times or providing a list in the . When multiple upstreams are used routing to them will be based on the path they are set up with. Every command line argument can be specified as an environment variable by prefixing it with `OAUTH2PROXY`, capitalising it, and replacing hyphens (`-`) with underscores (`_`). If the argument can be specified multiple times, the environment variable should be plural (trailing `S`). This is particularly useful for storing secrets outside of a configuration file or the command line. For example, the `--cookie-secret` flag becomes `OAUTH2PROXYCOOKIE_SECRET`, and the `--email-domain` flag becomes `OAUTH2PROXYEMAIL_DOMAINS`. By default, OAuth2 Proxy logs all output to stdout. Logging can be configured to output to a rotating log file using the `--logging-filename` command. If logging to a file you can also configure the maximum file size (`--logging-max-size`), age (`--logging-max-age`), max backup logs (`--logging-max-backups`), and if backup logs should be compressed (`--logging-compress`). There are three different types of logging: standard, authentication, and HTTP requests. These can each be enabled or disabled with `--standard-logging`, `--auth-logging`, and `--request-logging`. Each type of logging has its own configurable format and variables. By default these formats are similar to the Apache Combined Log. Logging of requests to the `/ping` endpoint (or using `--ping-user-agent`) and the `/ready` endpoint can be disabled with `--silence-ping-logging` reducing log volume. Authentication logs are logs which are guaranteed to contain a username or email address of a user attempting to authenticate. These logs are output by default in the below format: ``` <REMOTE_ADDRESS> - <REQUEST ID> - <user@domain.com> [19/Mar/2015:17:20:19 -0400] [<STATUS>] <MESSAGE> ``` The status block will contain one of the below strings: `AuthSuccess` If a user has authenticated successfully by any method `AuthFailure` If the user failed to authenticate explicitly `AuthError` If there was an unexpected error during authentication If you require a different format than that, you can configure it with the `--auth-logging-format` flag. The default format is configured as follows: ``` {{.Client}} - {{.RequestID}} - {{.Username}} [{{.Timestamp}}] [{{.Status}}] {{.Message}} ``` Available variables for auth logging: | Variable | Example | Description | | - | | -- | | Client | 74.125.224.72 | The client/remote IP

Will use the X-Real-IP header it if exists & reverse-proxy is set to true. | | Host | domain.com | The value of the Host header. | | Message | Authenticated via OAuth2 | The details of the auth attempt. | | Protocol | HTTP/1.0 | The request protocol. | | RequestID | 00010203-0405-4607-8809-0a0b0c0d0e0f | The request ID pulled from the `--request-id-header`. Random UUID if empty | | RequestMethod | GET | The request method. | | Timestamp | 19/Mar/2015:17:20:19 -0400 | The date and time of the logging event. | | UserAgent | - | The full user agent as reported by the requesting client. | | Username | username@email.com | The email or username of the auth request. | | Status | AuthSuccess | The status of the auth request. See above for details. | HTTP request logs will output by default in the below format: ``` <REMOTEADDRESS> - <REQUEST ID> - <user@domain.com> [19/Mar/2015:17:20:19 -0400] <HOSTHEADER> GET <UPSTREAMHOST> "/path/" HTTP/1.1 "<USERAGENT>" <RESPONSECODE> <RESPONSEBYTES> <REQUEST_DURATION> ``` If you require a different format than that, you can configure it with the `--request-logging-format` flag. The default format is configured as follows: ``` {{.Client}} - {{.RequestID}} - {{.Username}} [{{.Timestamp}}] {{.Host}} {{.RequestMethod}} {{.Upstream}} {{.RequestURI}} {{.Protocol}} {{.UserAgent}} {{.StatusCode}} {{.ResponseSize}} {{.RequestDuration}} ``` Available variables for request logging: | Variable | Example | Description | | | | -- | | Client | 74.125.224.72 | The client/remote IP address. Will use the X-Real-IP header it if exists & reverse-proxy is set to true. | | Host | domain.com | The value of the Host header. | | Protocol | HTTP/1.0 | The request protocol. | | RequestDuration | 0.001 | The time in seconds that a request took to process. | | RequestID | 00010203-0405-4607-8809-0a0b0c0d0e0f | The request ID pulled from the `--request-id-header`. Random UUID if empty | | RequestMethod | GET | The request method. | | RequestURI | "/oauth2/auth" | The URI path of the request. | | ResponseSize | 12 | The size in bytes of the response. | | StatusCode | 200 | The HTTP status code of the response. | | Timestamp | 19/Mar/2015:17:20:19 -0400 | The date and time of the logging event. | | Upstream | - | The upstream data of the HTTP request. | | UserAgent | - | The full user agent as reported by the requesting client. | | Username | username@email.com | The email or username of the auth request. | All other logging that is not covered by the above two types of logging will be output in this standard logging format. This includes configuration information at startup and errors that occur outside of a session. The default format is below: ``` [19/Mar/2015:17:20:19 -0400] [main.go:40] <MESSAGE> ``` If you require a different format than that, you can configure it with the `--standard-logging-format` flag. The default format is configured as follows: ``` [{{.Timestamp}}] [{{.File}}] {{.Message}} ``` Available variables for standard logging: | Variable | Example | Description | | | | -- | | Timestamp | 19/Mar/2015:17:20:19 -0400 | The date and time of the logging event. | | File | main.go:40 | The file and line number of the logging statement. | | Message | HTTP: listening on 127.0.0.1:4180 | The details of the log statement. | The allows Nginx to authenticate requests via the oauth2-proxy's `/auth` endpoint, which only returns a 202 Accepted response or a 401 Unauthorized response without proxying the request through. For example: ```nginx server { listen 443 ssl; server_name ...; include ssl/ssl.conf; location /oauth2/ { proxy_pass

proxysetheader Host $host; proxysetheader X-Real-IP $remote_addr; proxysetheader X-Scheme $scheme; proxysetheader X-Auth-Request-Redirect $request_uri; } location = /oauth2/auth { proxy_pass http://127.0.0.1:4180; proxysetheader Host $host; proxysetheader X-Real-IP $remote_addr; proxysetheader X-Scheme $scheme; proxysetheader Content-Length ""; proxypassrequest_body off; } location / { auth_request /oauth2/auth; errorpage 401 =403 /oauth2/signin; authrequestset $user $upstreamhttpxauthrequest_user; authrequestset $email $upstreamhttpxauthrequest_email; proxysetheader X-User $user; proxysetheader X-Email $email; authrequestset $token $upstreamhttpxauthrequestaccesstoken; proxysetheader X-Access-Token $token; authrequestset $authcookie $upstreamhttpsetcookie; addheader Set-Cookie $authcookie; authrequestset $authcookienameupstream1 $upstreamcookieauthcookiename_1; if ($auth_cookie ~ "(; .)") { set $authcookiename0 $authcookie; set $authcookiename1 "authcookiename1=$authcookienameupstream1$1"; } if ($authcookienameupstream1) { addheader Set-Cookie $authcookiename0; addheader Set-Cookie $authcookiename1; } proxy_pass http://backend/; } } ``` When you use ingress-nginx in Kubernetes, you MUST use `kubernetes/ingress-nginx` (which includes the Lua module) and the following configuration snippet for your `Ingress`. Variables set with `authrequestset` are not `set`-able in plain nginx config when the location is processed via `proxy_pass` and then may only be processed by Lua. Note that `nginxinc/kubernetes-ingress` does not include the Lua module. ```yaml nginx.ingress.kubernetes.io/auth-response-headers: Authorization nginx.ingress.kubernetes.io/auth-signin: https://$host/oauth2/start?rd=$escapedrequesturi nginx.ingress.kubernetes.io/auth-url: https://$host/oauth2/auth nginx.ingress.kubernetes.io/configuration-snippet: | authrequestset $nameupstream1 $upstreamcookiename_1; accessbylua_block { if ngx.var.nameupstream1 ~= "" then ngx.header["Set-Cookie"] = "name1=" .. ngx.var.nameupstream1 .. ngx.var.authcookie:match("(; .*)") end } ``` It is recommended to use `--session-store-type=redis` when expecting large sessions/OIDC tokens (e.g. with MS Azure). You have to substitute name with the actual cookie name you configured via --cookie-name parameter. If you don't set a custom cookie name the variable should be "$upstreamcookieoauth2proxy1" instead of "$upstreamcookiename1" and the new cookie-name should be "oauth2proxy1=" instead of "name1=". This option requires `--reverse-proxy` option to be set. The allows Traefik to authenticate requests via the oauth2-proxy's `/oauth2/auth` endpoint on every request, which only returns a 202 Accepted response or a 401 Unauthorized response without proxying the whole request through. For example, on Dynamic File (YAML) Configuration: ```yaml http: routers: a-service: rule: "Host(`a-service.example.com`)" service: a-service-backend middlewares: oauth-errors oauth-auth tls: certResolver: default domains: main: "example.com" sans: "*.example.com" oauth: rule: "Host(`a-service.example.com`, `oauth.example.com`) && PathPrefix(`/oauth2/`)" middlewares: auth-headers service: oauth-backend tls: certResolver: default domains: main: "example.com" sans: "*.example.com" services: a-service-backend: loadBalancer: servers: url: http://172.16.0.2:7555 oauth-backend: loadBalancer: servers: url: http://172.16.0.1:4180 middlewares: auth-headers: headers: sslRedirect: true stsSeconds: 315360000 browserXssFilter: true contentTypeNosniff: true forceSTSHeader: true sslHost: example.com stsIncludeSubdomains: true stsPreload: true frameDeny: true oauth-auth: forwardAuth: address: https://oauth.example.com/oauth2/auth trustForwardHeader: true oauth-errors: errors: status: "401-403" service: oauth-backend query: "/oauth2/sign_in?rd={url}" ``` Redirect to sign_in functionality provided without the use of `errors` middleware with pointing to oauth2-proxy service's `/` endpoint Following options need to be set on `oauth2-proxy`: `--upstream=static://202`: Configures a static response for authenticated sessions `--reverse-proxy=true`: Enables the use of `X-Forwarded-*` headers to determine redirects correctly ```yaml http: routers: a-service-route-1: rule: "Host(`a-service.example.com`, `b-service.example.com`) && PathPrefix(`/`)" service: a-service-backend middlewares: oauth-auth-redirect # redirects all unauthenticated to oauth2 signin tls: certResolver: default domains: main: "example.com" sans: "*.example.com" a-service-route-2: rule: "Host(`a-service.example.com`) && PathPrefix(`/no-auto-redirect`)" service: a-service-backend middlewares: oauth-auth-wo-redirect # unauthenticated session will return a 401 tls: certResolver: default domains: main: "example.com" sans: "*.example.com" services-oauth2-route: rule: "Host(`a-service.example.com`, `b-service.example.com`) && PathPrefix(`/oauth2/`)" middlewares: auth-headers service: oauth-backend tls: certResolver: default domains: main: "example.com" sans: "*.example.com" oauth2-proxy-route: rule: "Host(`oauth.example.com`) && PathPrefix(`/`)" middlewares: auth-headers service: oauth-backend tls: certResolver: default domains: main: "example.com" sans: "*.example.com" services: a-service-backend: loadBalancer: servers: url: http://172.16.0.2:7555 b-service-backend: loadBalancer: servers: url: http://172.16.0.3:7555 oauth-backend: loadBalancer: servers: url: http://172.16.0.1:4180 middlewares: auth-headers: headers: sslRedirect: true stsSeconds: 315360000 browserXssFilter: true contentTypeNosniff: true forceSTSHeader: true sslHost: example.com stsIncludeSubdomains: true stsPreload: true frameDeny: true oauth-auth-redirect: forwardAuth: address: https://oauth.example.com/ trustForwardHeader: true authResponseHeaders: X-Auth-Request-Access-Token Authorization oauth-auth-wo-redirect: forwardAuth: address: https://oauth.example.com/oauth2/auth trustForwardHeader: true authResponseHeaders: X-Auth-Request-Access-Token Authorization ``` :::note If you set up your OAuth2 provider to rotate your client secret, you can use the `client-secret-file` option to reload the secret when it is updated. :::