Uploaded image for project: 'OpenShift GitOps'
  1. OpenShift GitOps
  2. GITOPS-2469

Update docs for Keycloak

XMLWordPrintable

    • Icon: Task Task
    • Resolution: Done
    • Icon: Major Major
    • 1.7.0
    • None
    • Documentation
    • None
    • 5
    • False
    • None
    • False
    • GITOPS Sprint 232, GITOPS Sprint 233

      I would like to update the docs for keycloak configuration.

      https://docs.openshift.com/container-platform/4.11/cicd/gitops/configuring-sso-for-argo-cd-using-keycloak.html

      ```yaml
      apiVersion: argoproj.io/v1alpha1
      kind: ArgoCD
      metadata:
        name: example-argocd
        labels:
          example: basic
      spec:
        sso:
          provider: keycloak
          keycloak:
           rootCA: '<PEM encoded root certificate>'
        server:
          route:
           enabled: true
      ```

      If you wish to proceed with insecure connection then you can leave the value of rootCA empty and use skip verify as show below.

      ```
      apiVersion: argoproj.io/v1alpha1
      kind: ArgoCD
        metadata:
           name: example-argocd
        labels:
           example: basic
      spec:
        extraConfig:
          oidc.tls.insecure.skip.verify: 'true'
        sso:
          provider: keycloak
          keycloak:
            rootCA: ""
      ```

      Background:
      With a recent security fix, the certificate of RHSSO could not be validated when configured with a certificate not signed by one of the well-known certificate authorities.

      You can now provide a custom certificate to verify the KeyCloak's TLS certificate while communicating with it. In addition, you can add `rootCA` to the Argo CD custom resource `.spec.keycloak.rootCA` field. The Operator reconciles such changes and updates the `oidc.config in argocd-cm` config map with the PEM encoded root certificate.

      link: https://issues.redhat.com/browse/GITOPS-2214

            eromanov@redhat.com Eliska Romanova
            aveerama@redhat.com Abhishek Veeramalla
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated:
              Resolved: