Difference between revisions of "KC HTTP ENABLED"
Jump to navigation
Jump to search
Tags: Mobile web edit, Mobile edit |
|||
| Line 1: | Line 1: | ||
| − | KC_HTTP_ENABLED | + | KC_HTTP_ENABLED enables HTTP, if not only [[HTTPS]], see also [[start-dev]] |
[[kubectl set env]] [[statefulset/]]keycloak -n YOUR_NS \ | [[kubectl set env]] [[statefulset/]]keycloak -n YOUR_NS \ | ||
Latest revision as of 08:52, 19 June 2026
KC_HTTP_ENABLED enables HTTP, if not only HTTPS, see also start-dev
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-
extraEnvVars: - name: KEYCLOAK_EXTRA_ARGS value: "--import-realm" - name: KEYCLOAK_OVERWRITE_REALM value: "true" - name: KC_HTTP_ENABLED value: "true" - name: KC_PROXY_HEADERS value: "xforwarded"
start-dev
See also[edit]
KC_PROXY (deprecated), KC_HOSTNAME, KC_HOSTNAME_STRICT_HTTPS (deprecated), KC_HTTP_ENABLED, KC_PROXY_HEADERSkcadm.sh [ config credentials | get (users | clients) ],redirectUris, rootUrl, webOrigins,.keycloak/kcadm.config- KC env variables,
KC_BOOTSTRAP_ADMIN_USERNAME, KC_HOSTNAME, KC_HTTP_ENABLED, KC_PROXY_HEADERS
Advertising: