Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
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.
Description of problem:
Given registering a system "RHEL6.8 Snapshot4-1 variant Server" using proxy
Firstboot connects throught a non auth proxy even "use credentials" is checked on.
This is a little confusing since it opens a space to make inconsistent settings.
I (as a customer) wanted to use credentials for proxy but
I entered wrong proxy url (ie. no auth proxy).
And the program did not inform me about this inconsistency.
Version-Release number of selected component (if applicable):
RHEL6.8 Snapshot4-1 Server variant
How reproducible:
everytime
Steps to Reproduce:
Given Firstboot running at RHEL6.8 Snapshot4-1 - variant Server
When I clicked "Proxy Setup" at "Choose Service"
then proxy dialog appeared.
When I checked "I would like to connect via HTTP proxy"
and I filled "Proxy Location" using value for non auth proxy (auto-services.usersys.redhat.com:3129)
and I checked "Use Authentication with HTTP Proxy"
and I filled wrong/right credentials
and I clicked "Close"
then a dialog was closed.
When I clicked "Forward"
and I clicked "Forward" again
then a program connected throught a proxy even I checked "Use Authentication with HTTP Proxy" and filled credentials.
Actual results:
Program ignores an inconsistency of values entered in Proxy Dialog.
Expected results:
Program could inform me that I entered an url of a non auth proxy and I checked that I want to use authorization for proxy.
The proxy dialog used in firstboot belongs to rhn-client-tools.
Comment 5Gennadii Altukhov
2016-10-24 16:12:59 UTC
Looks like we will not fix this *bug*.
Technical details:
We use a python's httplib.HTTPConnection on a bottom level. Levels:
1) rpclib to communicate with Satellite/RHN
2) transport for rpclib ("ProxyTransport" in a case of HTTP proxy and credentials provided)
3) connection for transport. We use HTTPProxyConnection - this is just httplib.HTTPConnection with additional header "Proxy-Authorization: Basic <encoded_credentials>".
In a case when proxy doesn't require authentification it ignores this header and returns us a connection.
So we cannot catch this situation.
Comment 6RHEL Program Management
2016-10-24 17:56:29 UTC
Development Management has reviewed and declined this request.
You may appeal this decision by reopening this request.