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.

Bug 1595260

Summary: yum fails to connect over proxy with HTTPAUTH_ANY
Product: Red Hat Enterprise Linux 7 Reporter: Michal Dekan <mdekan>
Component: yumAssignee: Packaging Maintenance Team <packaging-team-maint>
Status: CLOSED WONTFIX QA Contact: BaseOS QE Security Team <qe-baseos-security>
Severity: medium Docs Contact:
Priority: unspecified    
Version: 7.5CC: james.antill, jpasqual, kdudka, ktordeur, mdomonko
Target Milestone: rc   
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2019-09-02 12:31:07 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On:    
Bug Blocks: 1716963, 1719445    

Comment 2 Kamil Dudka 2018-06-28 11:44:54 UTC
There was a similar bug reported (and already closed) upstream about --proxy-anyauth not working as expected when multiple authentication methods are offered by a proxy:

https://github.com/curl/curl/issues/876

While the logic behind --proxy-anyauth could be improved to cover more scenarios, the most reliable solution is to ask (lib)curl explicitly to authenticate via NTLM when NTLM is needed to connect through a proxy.

Comment 3 Michal Dekan 2018-07-04 11:09:21 UTC
Customer from attached case confirmed that this modification helped him to bypass  error 407 when connecting to cdn over proxy which supports Basic and NTLM authorization. It forces Basic authorization.

Will create KCS as well.

/usr/lib/python2.7/site-packages/urlgrabber/grabber.py

~~~
1481                 # All but Kerberos.  BZ 769254
1482                 #pycurl.HTTPAUTH_ANY - pycurl.HTTPAUTH_GSSNEGOTIATE)-----> commenting this line
1483                 pycurl.HTTPAUTH_BASIC) ------------> adding this line
1484         
1485         if opts.username and opts.password:
1486             if self.scheme in ('http', 'https'):
~~~

Comment 4 Kamil Dudka 2018-11-09 16:33:07 UTC
The upstream issue has been close and the bug described in the KNOWN_BUGS file:

https://github.com/curl/curl/commit/10c91b66#diff-b97570cc6a6d2d180356338a9ccffee0R451