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

Add dedicated docs page for API Tokens under "Integrating" section

XMLWordPrintable

    • Icon: Feature Request Feature Request
    • Resolution: Done
    • Icon: Normal Normal
    • None
    • None
    • None
    • False
    • None
    • False

      What is the nature and description of the request?

      Currently there are various mentions of using an API token for integrations, authenticating using roxctl, and API based operations, but they do not have their own dedicated section in the GUI that

      1. Describe what they are in detail and why they are used. 
      2. Their different uses and why you would use them in a succinct section 
        1. API-based operations
        2. Roxctl
        3. CICD workflows
        4. Permissions/Roles assignment 
      3. TTL on API-tokens. How to change this if possible? 
      4. Any other best practices 

      Why does the customer need this? (List the business requirements here)

      Many customers use basic auth for API based operations resulting in overly permissive operations using the Admin account. Other customers have questions like: "What is the TTL on the tokens?" "How do we assign permissions and roles to tokens?", "Where should we store these tokens?", etc... Having a single page that reflects everything would be helpful.

              kcarmich@redhat.com Kerry Carmichael
              ebannon@redhat.com Eric Bannon (Inactive)
              Anjali Telang, Boaz Michaely, Doron Caspin, JP Jung, Maria Simon Marcos, Shubha Badve
              ACS Docs
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Created:
                Updated:
                Resolved: