Details

    • Steps to Reproduce:
      Hide

      https://github.com/wuerzelchen/KeycloakCertManager

      git clone https://github.com/wuerzelchen/KeycloakCertManager.git
      cd KeycloakCertManager
      #install custom resource definitions:
      kubectl apply -f https://raw.githubusercontent.com/jetstack/cert-manager/release-0.8/deploy/manifests/00-crds.yaml
      helm init --history-max 200
      helm dependencies update
      #add your hostname for the tls certificate to templates/http-keycloak-ingress.yaml
      helm upgrade --install -f values.yaml ./

      browse to the given url and see the redirects

      Show
      https://github.com/wuerzelchen/KeycloakCertManager git clone https://github.com/wuerzelchen/KeycloakCertManager.git cd KeycloakCertManager #install custom resource definitions: kubectl apply -f https://raw.githubusercontent.com/jetstack/cert-manager/release-0.8/deploy/manifests/00-crds.yaml helm init --history-max 200 helm dependencies update #add your hostname for the tls certificate to templates/http-keycloak-ingress.yaml helm upgrade --install -f values.yaml ./ browse to the given url and see the redirects
    • Docs QE Status:
      NEW
    • QE Status:
      NEW

      Description

      When I try to access my keycloak service via an nginx-ingress with TLS termination, it always redirects in an endless loop with a 304 message.
      I tripple checked that I have PROXY_ADDRESS_FORWARDING set to true.

        Gliffy Diagrams

          Attachments

            Activity

              People

              • Assignee:
                Unassigned
                Reporter:
                wuerzelchen Wolfgang Ladermann
              • Votes:
                0 Vote for this issue
                Watchers:
                3 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: