[Support]: Cookie Refresh Behaviour
Author: GianluCreated Aug 28, 2026Updated Aug 28, 2026
Labelshelp wantedconfiguration
OAuth2-Proxy Version
7.15.3
Provider
keycloak-oidc
Current Behaviour of your Problem
Cookie expires is only refreshed hitting the /oauth2/signin (/oauth2/sign_in as per docs is not working) page.
Configuration details or additional information
# # cookie_secret = "" <- env
skip_auth_strip_headers = true
reverse_proxy = true
# # client_id = "" <- env
# # client_secret = "" <- env
# # oidc_issuer_url = "" <- env
email_domains = "*"
code_challenge_method = "S256"
http_address = "0.0.0.0:4180"
upstreams = [
"static://200"
]
session_store_type = "redis"
exclude_logging_paths = "/ping,/ready"
# # redis_connection_url = "" <- env
cookie_httponly = true
real_client_ip_header = "X-Forwarded-For"
pass_access_token = true
pass_authorization_header = true
set_xauthrequest = true
pass_user_headers = true
show_debug_on_error = true
skip_jwt_bearer_tokens = false
skip_provider_button = true
cookie_secure = true
pass_host_header = true
skip_auth_preflight = true
cookie_refresh = "3m" # <- env
cookie_expire = "10m" # <- env
silence_ping_logging = trueSteps To Reproduce
If I browse a page (I'm testing with the traefik/whoami), if I'm out of refresh_cookie period, Redis Session TTL is updated but I don't receive a set-cookie with the new timestamp.
If I hit /oauth2/signin, I see in log the refresh procedure in logs and I receive a set cookie with the new timestamp.
Source: oauth2-proxy/oauth2-proxy