Keycloak behind kong ingress controller with https

Question

We are setting up keycloak behind the kong ingress controller with https. The https communication got enabled with self signed certificate. We are able access keycloak with https enabled. The welcome page is getting loaded without any issues. But the problem is the sub sequent call becomes http intead of https, http://172.21.25.10:30007/auth/admin/… instead of https://172.21.25.10:30007/auth/admin/…

I have set up frontend url in master realm settings

We need the admin console with https access. How to make sub sequent call with https in keycloak.

- name: KEYCLOAK_HTTP_RELATIVE_PATH
  value: /auth/
- name: KAFKA_URL
  value: kafka:9092
- name: KEYCLOAK_FRONTEND_URL
  value: https://hostname:30007/auth
- name: KC_PROXY_ADDRESS_FORWARDING
  value: “true”
- name: KC_PROXY_HEADERS
  value: xforwarded
- name: KC_HOSTNAME_STRICT_HTTPS
  value: “false”
- name: KC_HTTP_ENABLED
  value: “true”
- name: KC_LOG_LEVEL
  value: DEBUG

Please find the current configuration below:

We are using Keycloak behind kong ingress controller with https

Still we are getting the same issue.

keycloak-ingress file:[kong version: 2.4.0]

apiVersion: networking.k8s.io/v1
kind: Ingress
metadata:
  name: keycloak-ingress
  labels:
    app.kubernetes.io/instance: kong
    app.kubernetes.io/managed-by: Helm
  annotations:
    konghq.com/strip-path: "false"
    kubernetes.io/ingress.class: "kong"
    konghq.com/protocols: "https"
spec:
  ingressClassName: kong
  rules:
    #- host: freshxcom.mt.mtnet
    - http:
        paths:
        - path: /auth
          pathType: Prefix
          backend:
            service:
              name: keycloak
              port:
                number: 80

keycloak bitnami helm chart: 18.0.2 keycloak values file: keycloak-values.yaml

httpRelativePath: "/auth/"
extraEnvVars: |
  - name: KAFKA_URL
    value: kafka:9092
  - name: KEYCLOAK_FRONTEND_URL
    value: "https://freshxcom.mt.mtnet:30007/auth"
  - name: PROXY_ADDRESS_FORWARDING
    value: "true"
  - name: KC_LOG_LEVEL
    value: DEBUG

Keycloak behind kong ingress controller with https

0 Answers0