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
Copy file name to clipboardExpand all lines: config/README.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -87,7 +87,7 @@ via the standard authorization code grant flow from an OIDC Provider.
87
87
| idle_session_timeout |[uint32](#uint32)|| The Authservice associates obtained OIDC tokens with a session ID in a session store. It also stores some temporary information during the login process into the session store, which will be removed when the user finishes the login. This configuration option sets the number of seconds since the most recent incoming request from that user until the user's session with the Authservice should expire. When configured to `0`, which is the default value, session expiration will not consider idle time, but can still consider timeout based on maximum absolute time since added. When both `absolute_session_timeout` and `idle_session_timeout` are zero, then sessions will never expire. These settings do not affect how quickly the OIDC tokens contained inside the user's session expire. Optional. |
88
88
| trusted_certificate_authority |[string](#string)|| String PEM-encoded certificate authority to trust when performing HTTPS calls to the OIDC Identity Provider. Optional. |
89
89
| trusted_certificate_authority_file |[string](#string)|| The file path to the PEM-encoded certificate authority to trust when performing HTTPS calls to the OIDC Identity Provider. Optional. |
90
-
| trusted_certificate_authority_refresh_interval |[google.protobuf.Duration](#google-protobuf-Duration)|| The duration between refreshes of the trusted certificate authority if `trusted_certificate_authority_file` is set. Unset or 0 (the default) disables the refresh, useful is no rotation is expected. Is a String that ends in `s` to indicate seconds and is preceded by the number of seconds, e.g. `120s` (represents 2 minutes). Optional. |
90
+
| trusted_certificate_authority_refresh_interval |[google.protobuf.Duration](#google-protobuf-Duration)|| The duration between refreshes of the trusted certificate authority if `trusted_certificate_authority_file` is set. Unset or 0 (the default) disables the refresh, useful is no rotation is expected. Is a String that ends in `s` to indicate seconds and is preceded by the number of seconds, e.g. `120s` (represents 2 minutes). Optional. Deprecated. The file will be automatically reloaded when it changes. |
91
91
| proxy_uri | [string](#string) | | The Authservice makes two kinds of direct network connections directly to the OIDC Provider. Both are POST requests to the configured `token_uri` of the OIDC Provider. The first is to exchange the authorization code for tokens, and the other is to use the refresh token to obtain new tokens. Configure the `proxy_uri` when both of these requests should be made through a web proxy. The format of `proxy_uri` is `http://proxyserver.example.com:8080`, where `:<port_number>` is optional. Userinfo (usernames and passwords) in the `proxy_uri` setting are not yet supported. The `proxy_uri` should always start with `http://`. The Authservice will upgrade the connection to the OIDC provider to HTTPS using an HTTP CONNECT request to the proxy server. The proxy server will see the hostname and port number of the OIDC provider in plain text in the CONNECT request, but all other communication will occur over an encrypted HTTPS connection negotiated directly between the Authservice and the OIDC provider. See also the related `trusted_certificate_authority` configuration option. Optional. |
92
92
| redis_session_store_config |[RedisConfig](#authservice-config-v1-oidc-RedisConfig)|| When specified, the Authservice will use the configured Redis server to store session data. Optional. |
93
93
| skip_verify_peer_cert |[google.protobuf.Value](#google-protobuf-Value)|| If set to true, the verification of the destination certificate will be skipped when making a request to the Token Endpoint. This option is useful when you want to use a self-signed certificate for testing purposes, but basically should not be set to true in any other cases. Optional. keep this field out from the trusted_ca_config one of for backward compatibility. |
0 commit comments