public_git/oauth2-proxy
1
0
Fork 0
mirror of https://github.com/oauth2-proxy/oauth2-proxy.git synced 2026-10-19 16:23:41 +02:00
Code Issues Projects Releases Wiki Activity

doc: cncf onboarding and sponsor update

Browse Source 
Signed-off-by: Jan Larwig <jan@larwig.com>
This commit is contained in:
Jan Larwig
2026-01-17 11:04:43 +01:00
parent 34c2712c99
commit f46dcc77a8
15 changed files with 215 additions and 167 deletions
Download Patch File Download Diff File Expand all files Collapse all files
docs/versioned_docs/version-7.14.x/configuration/sessions.md
+2 -2
View File
@@ -64,9 +64,9 @@ the refresh flow to get a new Access-Token. If it is longer, it might be that th
expired.
The "cookie-refresh" value controls when OAuth2 Proxy tries to refresh an Access-Token. If it is set to "0", the
Access-Token will never be refreshed, even if it is already expired and a valid Refresh-Token is available. If set, OAuth2-Proxy will
Access-Token will never be refreshed, even if it is already expired and a valid Refresh-Token is available. If set, OAuth2 Proxy will
refresh the Access-Token after this many seconds whether it is still valid or not. According to the official OAuth2.0 specification
Access-Tokens are not required to follow a specific format. Therefore OAuth2-Proxy cannot check for any expiry date without an
Access-Tokens are not required to follow a specific format. Therefore OAuth2 Proxy cannot check for any expiry date without an
introspection endpoint. If an Access-Token expires and you have not set a corresponding "cookie-refresh" value, you will likely
encounter expiry issues.