Red Hat Satellite engineering is moving the tracking of its product development work on Satellite to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "Satellite project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs will be migrated starting at the end of May. If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "Satellite project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/SAT-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 2241442 - [RFE] Ability to list and revoke Global Registration tokens
Summary: [RFE] Ability to list and revoke Global Registration tokens
Keywords:
Status: CLOSED DUPLICATE of bug 1919979
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Registration
Version: 6.12.0
Hardware: x86_64
OS: Linux
unspecified
medium
Target Milestone: Unspecified
Assignee: satellite6-bugs
QA Contact: Satellite QE Team
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2023-09-30 00:09 UTC by Jessica Richards
Modified: 2023-10-03 11:31 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2023-10-03 11:31:40 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker SAT-20507 0 None None None 2023-09-30 00:11:56 UTC

Description Jessica Richards 2023-09-30 00:09:28 UTC
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


Note You need to log in before you can comment on or make changes to this bug.