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

Evaluate configuration of dex in gitops operator to not use service account token as OAUTH

XMLWordPrintable

    • Icon: Epic Epic
    • Resolution: Done
    • Icon: Normal Normal
    • 1.7.0
    • None
    • Operator
    • None
    • Avoid Default Service Account Token use for dex configuration
    • 5
    • False
    • Hide

      None

      Show
      None
    • False
    • To Do

      Gitops operator currently enables dex by default and it uses service account as oauth client and uses service account secret as oauth token, since from k8s v1.24, service account associated with dex pods will not have secret auto mounted , however token is populated by k8s, as a result gitops operator need to create the secret and mount it in dex service account.

       

      But this is not the recommended way by kubernetes 

      Kubernetes says to use TokenRequest API to get the token for service account , that will  have time based expiry and should be refreshed as in when used.

       

      Acceptance Criteria

      1) Come up with a way that dex can use service account as oauth client but self requests the Token and we don't need to fetch token from secret and pass it to dex to work, dex should manage this on its own, Probably dex must have implemented TokenRequest API we need to read dex documentation and see what configuration change gitops operator does.

      OR

      2) We can get rid of usage of service account as oauth client for dex and look for alternate configurations

       

       

       

              rismishr Rishabh Mishra (Inactive)
              rismishr Rishabh Mishra (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

                Created:
                Updated:
                Resolved: