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.
This is an offshoot of:
https://bugzilla.redhat.com/show_bug.cgi?id=1719175
for the specific case of the $ character. We resolved a large set of special characters in the original bug but are still unable to use the $ in passwords.
This bug is to track resolution and support for specifying a $ in the proxy password.
I fixed this in v2.2.9 of the redhat_access gem. It looks like BZ1719175 was included in snap 23 for Satellite 6.6 but with an old version of the gem? Not sure what happened but I'll look into it...
- Rex
We didn't really resolve the core issue in BZ1719175 so we are going to close this one out and unify on that bug. We hope to get that fixed in 6.7 as well as 6.6.z
*** This bug has been marked as a duplicate of bug 1719175 ***