RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 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 "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". 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 "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-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.

I was looking at the new subscription UI in the GNOME control center that Kalev Lember and Allan Day has been working on for RHEL Workstation in https://bugzilla.redhat.com/show_bug.cgi?id=1720251

One part of the design I though was nice and clear is how it's breaking up the inputs into user+pass authentication and activation keys. If I'm reading the docs right, if you use the activation key registration method, you only need the key and organization fields set, but not the username+password.
https://access.redhat.com/solutions/3341191

In the current cockpit web console UI it makes it look like you always have to fill all four fields, when the activation key and username+password is mutually exclusive.

Also from the man page.

When the --activationkey option is used, it is not necessary  to
use the --username and --password options, because the authenti‐
cation information is implicit in the activation key.

Design proposal:
https://raw.githubusercontent.com/cockpit-project/cockpit-design/1cfad8e618710072d5793c9bafa742d5e4eb4472/subscriptions/subscription-authentication.png

It works. 
It looks really nice and it is pretty great improvement comparing previous form template.

BTW: I have tried that user can use activation key to register system too.

screenshots attached.

Thanks.

Created attachment 1701175 [details]
Register System dialog - 01

Created attachment 1701176 [details]
Register System dialog - 02

Looks awesome, thanks!

Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory (subscription-manager bug fix and enhancement update), and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHBA-2020:4460