Hide Forgot
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.
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.
Development Management has reviewed and declined this request. You may appeal this decision by reopening this request.