Uploaded image for project: 'OpenShift Request For Enhancement'
  1. OpenShift Request For Enhancement
  2. RFE-8298

Move non expiring token for the service-account `openshift-gitops-argocd-dex-server` to an expiring one

XMLWordPrintable

    • Icon: Feature Request Feature Request
    • Resolution: Unresolved
    • Icon: Major Major
    • None
    • None
    • GitOps
    • None
    • None
    • Product / Portfolio Work
    • None
    • False
    • Hide

      None

      Show
      None
    • None
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      Proposed title of this feature request.
      Move non expiring token for the service-account `openshift-gitops-argocd-dex-server` to an expiring one.

      What is the nature and description of the request?
      Service-account `openshift-gitops-argocd-dex-server auto generates a non expiring token,
      Implement solution to move to an expiring token.

      Why does the customer need this? (List the business requirements here)
      Compliance :
      Non expiring Service account tokens are NOT auto generated by the OpenShift Platform anymore , GitOps Operator should follow the same OpenShift guidelines.

      How would the customer like to achieve this? (List the functional requirements here)
      Need solution from Red Hat.

      For each functional requirement listed, specify how Red Hat and the customer can test to confirm the requirement is successfully implemented.
      No auto generation of non expiring service account tokens.

      Would the customer be able to assist in testing this functionality if implemented?
      Yes

              halawren@redhat.com Harriet Lawrence
              rhn-support-dkarde Dipak Karde
              None
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Created:
                Updated:
                None
                None