Uploaded image for project: 'Satellite'
  1. Satellite
  2. SAT-20507

[RFE] Ability to list and revoke Global Registration tokens

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Unresolved
    • Icon: Normal Normal
    • None
    • 6.12.0
    • Registration
    • None
    • 0
    • False
    • Hide

      None

      Show
      None
    • False
    • CLOSED
    • 900
    • Rocket
    • Moderate
    • None

      1. Proposed title of this feature request

      [RFE] Ability to list Global Registration tokens and to revoke individual tokens

      3. What is the nature and description of the request?

      Customers would like to be able list the active Glogal Registration tokens. Once they have this information, they will also want to be able to recover the literal tokens, to list the properties of individual tokens, and to revoke individual tokens, because that is the purpose of asking to view this information.

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

      A global registration token represents a passwordless point of access to the Satellite server. Lacking visibility to tokens that have been created, and lacking the ability to revoke such tokens, represents a theoretical security risk.

      5. How would the customer like to achieve this? (List the functional requirements here)

      Maybe under Content > Lifecycle, underneath "Activation Keys", we could add an entry for "Global Registration tokens".

      6. For each functional requirement listed, specify how Red Hat and the customer can test to confirm the requirement is successfully implemented.

      • create a new token
      • check the new view to verify that the token is present
      • copy the token from that view and use it to register a host
      • inspect the properties listed for that token and verify that they match the properties of the registered host
      • delete the token
      • try to register a host to verify that the token no longer works

      7. Is there already an existing RFE upstream or in Red Hat Bugzilla?

      Bugzilla 1920184 was similar, but it was submitted for version 6.9 beta and not implemented.

      8. Does the customer have any specific timeline dependencies and which release would they like to target (i.e. RHEL8, RHEL9)?

      no

      9. Is the sales team involved in this request and do they have any additional input?

      no

      10. List any affected packages or components.

      foreman

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

      no

            jira-bugzilla-migration RH Bugzilla Integration
            jira-bugzilla-migration RH Bugzilla Integration
            RH Bugzilla Integration RH Bugzilla Integration
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated: