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.

Description of problem:

Trying to create an http proxy with a password of:

'foo#@' 

will not work correctly

Version-Release number of selected component (if applicable):
6.7.0

How reproducible:
always

Steps to Reproduce:
1. Attempt to create an http proxy with a password of 'foo#@' 
2. Try to test the proxy or use it for ec2 communication 

Actual results:
'bad password component'

Expected results:
works as expected


Additional info:
This doesn't appear at first glance to affect repository syncing, but more testing needs to be done

This bugzilla was opened based upon : bug 1825930#c12

After digging into it a bit more, i think the only thing that is not working is:

1) the 'test connection' button
2) the redhat access plugin (associated with BZ1825930)

So i think this BZ is really just tied to the 'test connection' button.  I tested AWS access and pulp2 repo syncing, and both worked fine with an http proxy created via the webUI.  The test connection button not working, does give the impression that it won't work. 

I do not consider this a regression.

Hi, we were unable to reproduce the issue on the latest version of Satellite.
As a result, I am closing the BZ ticket. However, please note that if the issue reoccurs or if additional information becomes available, we can reopen the ticket for further investigation.