[[How To Fix Yum Basic HTTP Authentication Behind a Proxy]]
You are here: Home » How To » How To Fix Yum Basic HTTP Authentication Behind a Proxy
Show page
AdminRecent ChangesSitemap

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Next revision		Previous revision
Last revisionBoth sides next revision
howto:how_to_fix_yum_basic_auth_behind_a_proxy [2015/03/24 21:26] – created smarkhowto:how_to_fix_yum_basic_auth_behind_a_proxy [2015/03/24 21:33] – [Resolution] smark
Line 1: Line 1:
 ====== How To Fix Yum Basic HTTP Authentication Behind a Proxy ====== ====== How To Fix Yum Basic HTTP Authentication Behind a Proxy ======
  
-====== Problem ======+===== Problem =====
 When configuring a yum proxy via /etc/yum.conf a "yum check-update" fails on the rhel6-some-repo-x.y repository with: When configuring a yum proxy via /etc/yum.conf a "yum check-update" fails on the rhel6-some-repo-x.y repository with:
  [root@myhost yum.repos.d]# yum check-update  [root@myhost yum.repos.d]# yum check-update
Line 10: Line 10:
  Error: Cannot retrieve repository metadata (repomd.xml) for repository: rhel6-some-repo-x.y. Please verify its path and try again  Error: Cannot retrieve repository metadata (repomd.xml) for repository: rhel6-some-repo-x.y. Please verify its path and try again
  
-====== Additional Information ======+===== Additional Information =====
 The customer used a cloud-based proxy service (ZScaler) but has NOT implemented proxy authentication. The proxy is configured correctly in /etc/yum.conf The customer used a cloud-based proxy service (ZScaler) but has NOT implemented proxy authentication. The proxy is configured correctly in /etc/yum.conf
  
-====== Troubleshooting ======+===== Troubleshooting =====
 A packet capture indicated the following HTTP header when requesting the repository information: A packet capture indicated the following HTTP header when requesting the repository information:
  GET http://REDACTED:REDACTED@yum.whatever.com/yum/base/repodata/repomd.xml HTTP/1.1  GET http://REDACTED:REDACTED@yum.whatever.com/yum/base/repodata/repomd.xml HTTP/1.1
- Authorization: Basic Y203MHVzZXI6bmtsMzJhOGtwMWNudw==+ Authorization: Basic REDACTED
  User-Agent: urlgrabber/3.9.1 yum/3.2.29  User-Agent: urlgrabber/3.9.1 yum/3.2.29
  Host: yum.whatever.com  Host: yum.whatever.com
  Accept: */*  Accept: */*
  Proxy-Connection: Keep-Alive  Proxy-Connection: Keep-Alive
 +
 A GET HTTP request in this format is malformed and therefore return a "400 Bad request" A GET HTTP request in this format is malformed and therefore return a "400 Bad request"
 +
 Further investigation revealed Yum's documentation recommends the following configuration when implementing HTTP authentication for a yum repository: Further investigation revealed Yum's documentation recommends the following configuration when implementing HTTP authentication for a yum repository:
 +
  baseurl=http://yum.whatever.com/yum/base/  baseurl=http://yum.whatever.com/yum/base/
  username=REDACTED  username=REDACTED
  password=REDACTED  password=REDACTED
 +
 Running the "yum check-update" command again reveals a different error: Running the "yum check-update" command again reveals a different error:
 +
  [root@myhost yum.repos.d]# yum check-update  [root@myhost yum.repos.d]# yum check-update
  Loaded plugins: priorities, refresh-packagekit, rhnplugin, security  Loaded plugins: priorities, refresh-packagekit, rhnplugin, security
Line 33: Line 38:
  Trying other mirror.  Trying other mirror.
  Error: Cannot retrieve repository metadata (repomd.xml) for repository: rhel6-some-repo-x.y. Please verify its path and try again  Error: Cannot retrieve repository metadata (repomd.xml) for repository: rhel6-some-repo-x.y. Please verify its path and try again
 +
 A packet capture shows the following HTTP request: A packet capture shows the following HTTP request:
 +
  GET http://REDACTED:REDACTED@yum.whatever.com/yum/base/repodata/repomd.xml HTTP/1.1  GET http://REDACTED:REDACTED@yum.whatever.com/yum/base/repodata/repomd.xml HTTP/1.1
- Authorization: Basic Y203MHVzZXI6bmtsMzJhOGtwMWNudw==+ Authorization: Basic REDACTED
  User-Agent: urlgrabber/3.9.1 yum/3.2.29  User-Agent: urlgrabber/3.9.1 yum/3.2.29
  Host: yum.whatever.com  Host: yum.whatever.com
Line 41: Line 48:
  Proxy-Connection: Keep-Alive  Proxy-Connection: Keep-Alive
  Resolution:  Resolution:
 +
 Because there is "Basic" authentication but no credentials supplied, the web server responds with "401 Authorization Required". Because there is "Basic" authentication but no credentials supplied, the web server responds with "401 Authorization Required".
 +
 The problem was tracked to an incompatibility with yum-3.2.29-60 and python-urlgrabber-3.9.1-9. The problem was tracked to an incompatibility with yum-3.2.29-60 and python-urlgrabber-3.9.1-9.
 +
 More information: More information:
   * https://issues.sonatype.org/browse/NEXUS-6007   * https://issues.sonatype.org/browse/NEXUS-6007
   * https://bugzilla.redhat.com/show_bug.cgi?id=739860   * https://bugzilla.redhat.com/show_bug.cgi?id=739860
 +
 This problem currently exists in RHEL 6.6 but may be resolved in a future version. It likely exists on any system with the python-urlgrabber-3.9.1-9 package. This problem currently exists in RHEL 6.6 but may be resolved in a future version. It likely exists on any system with the python-urlgrabber-3.9.1-9 package.
  
-====== Resolution ====== +===== Resolution ===== 
-Modify /etc/yum.repos.d/rhel6-some-repo-x.y.repo to conform to yum's recommended standard of baseurl/username/password for both contained repositories. + 
-Apply the patch as documented in the NEXUS URL. +  - Modify /etc/yum.repos.d/rhel6-some-repo-x.y.repo to conform to yum's recommended standard of baseurl/username/password for both contained repositories. 
- Copy the file urlgrabber.patch to the /root/ directory. +  - Apply the patch as documented in the NEXUS URL: 
- Back up the existing grabber.py file: +  - Copy the file {{:howto:urlgrabber.patch|}} to the /root/ directory. 
- cp /usr/lib/python2.6/site-packages/urlgrabber/grabber.py /root/urlgrabber_backup/head_node/grabber.py +  - Back up the existing grabber.py file: 
- Patch the file: + cp /usr/lib/python2.6/site-packages/urlgrabber/grabber.py /root/urlgrabber_backup/head_node/grabber.py 
- patch /usr/lib/python2.6/site-packages/urlgrabber/grabber.py < /root/urlgrabber.patch +  - Patch the file: 
- Each command should return an output similar to below: + patch /usr/lib/python2.6/site-packages/urlgrabber/grabber.py < /root/urlgrabber.patch 
- patching file /usr/lib/python2.6/site-packages/urlgrabber/grabber.py +  - Each command should return an output similar to below: 
- Hunk #2 succeeded at 426 (offset -5 lines). + patching file /usr/lib/python2.6/site-packages/urlgrabber/grabber.py 
- Hunk #3 succeeded at 828 (offset -6 lines). + Hunk #2 succeeded at 426 (offset -5 lines). 
- Hunk #4 succeeded at 1253 (offset -9 lines). + Hunk #3 succeeded at 828 (offset -6 lines). 
- Hunk #5 succeeded at 1349 (offset -9 lines). + Hunk #4 succeeded at 1253 (offset -9 lines). 
-Re-run the "yum check-update" command. It should complete successfully.+ Hunk #5 succeeded at 1349 (offset -9 lines). 
 +  - Re-run the "yum check-update" command. It should complete successfully.
howto/how_to_fix_yum_basic_auth_behind_a_proxy.txt · Last modified: 2015/03/24 21:33 by smark
Show pageOld revisions
Media ManagerBack to top
Driven by DokuWiki Recent changes RSS feed Valid CSS Valid XHTML 1.0