KC PROXY (deprecated)

KC_PROXY=edge,  implied HTTP enabled. (deprecated in Keycloak 24.0.0 (released in March 2024) in favour of KC_PROXY_HEADERS)

--proxy (ref) deprecated in favour of --proxy-headers (KC_PROXY_HEADERS)
Proxy: in helm show values bitnami/keycloak

v2 (KC 26)

KC_PROXY_HEADERS=xforwarded (or forwarded) + KC_HTTP_ENABLED=true

Non-secure context detected; cookies are not secured, and will not be available in cross-origin POST requests

KC_HOSTNAME_STRICT_HTTPS also deprecated

kubectl set env statefulset/keycloak -n YOUR_NS \
  KC_HOSTNAME=https://keycloak.subdomain.example.com \
  KC_HTTP_ENABLED=true \
  KC_PROXY_HEADERS=xforwarded \
  KC_HOSTNAME_STRICT_HTTPS- \
  KC_PROXY-

Related

• KC_HTTP_ENABLED
• KC_HOSTNAME_STRICT
• KC_HOSTNAME_STRICT_HTTPS (deprecated in v2)
• Okta backchannel

See also

• KC_PROXY (deprecated), KC_HOSTNAME, KC_HOSTNAME_STRICT_HTTPS (deprecated), KC_HTTP_ENABLED, KC_PROXY_HEADERS
• KC env variables, KC_BOOTSTRAP_ADMIN_USERNAME, KC_HOSTNAME, KC_HTTP_ENABLED, KC_PROXY_HEADERS
• Keycloak versions