Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.
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 2229331

Summary: The customer would like to see the curl commands created via global registration
Product: Red Hat Satellite Reporter: Waldirio M Pinheiro <wpinheir>
Component: RegistrationAssignee: satellite6-bugs <satellite6-bugs>
Status: CLOSED MIGRATED QA Contact: Satellite QE Team <sat-qe-bz-list>
Severity: high Docs Contact:
Priority: unspecified    
Version: 6.13.3CC: ahumbe, dsinglet, lstejska, msunil, mveiga, rlavi, saydas
Target Milestone: UnspecifiedKeywords: FutureFeature, MigratedToJIRA, Triaged
Target Release: Unused   
Hardware: All   
OS: All   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2024-06-06 16:26:07 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Waldirio M Pinheiro 2023-08-05 00:39:42 UTC
Description of problem:
The customer would like to see the curl commands created via global registration with all the parameters, for reuse purposes. Instead, it's necessary to recreate the command all the time, assuming the customer doesn't make any notes.

Also, assuming that keys are created with no expiration date, they will be around, and eventually, no one will be able to tell what are them, once there is no way to retrieve them.

Version-Release number of selected component (if applicable):
All of them with this feature.

How reproducible:
100%

Steps to Reproduce:
1. Create the global registration key
2. Leave the page
3.

Actual results:
There is no way to retrieve the curl command once again for reuse.

Expected results:
Be able to list all the commands, with all the parameters already set.

Additional info:

Comment 1 Sayan Das 2023-08-05 06:06:01 UTC
CC'ing Manu, who may have a customer requesting this 

And everyone in support almost every day asks for something like this.

In addition to that,

A user should be able to see :

* What all tokens were created for global registration ( only if they are still active )

* When they were created

* What is their expiry date


The jwt_secrets table shows when it was created and updated but not the expiry of the same.

Comment 2 Leos Stejskal 2023-08-08 12:39:32 UTC
Possibly duplicate to https://bugzilla.redhat.com/show_bug.cgi?id=1920184,
however, I'll keep it open as it has been requested already few times.

Comment 3 Eric Helms 2024-06-06 16:26:07 UTC
This BZ has been automatically migrated to the issues.redhat.com Red Hat Issue Tracker. All future work related to this report will be managed there.

Due to differences in account names between systems, some fields were not replicated.  Be sure to add yourself to Jira issue's "Watchers" field to continue receiving updates and add others to the "Need Info From" field to continue requesting information.

To find the migrated issue, look in the "Links" section for a direct link to the new issue location. The issue key will have an icon of 2 footprints next to it, and begin with "SAT-" followed by an integer.  You can also find this issue by visiting https://issues.redhat.com/issues/?jql= and searching the "Bugzilla Bug" field for this BZ's number, e.g. a search like:

"Bugzilla Bug" = 1234567

In the event you have trouble locating or viewing this issue, you can file an issue by sending mail to rh-issues. You can also visit https://access.redhat.com/articles/7032570 for general account information.