Bug 1174948
| Summary: | [RFE] Have Pulp support Basic Authentication in Repo URL's | ||||||
|---|---|---|---|---|---|---|---|
| Product: | Red Hat Satellite | Reporter: | Thom Carlin <tcarlin> | ||||
| Component: | Content Management | Assignee: | Justin Sherrill <jsherril> | ||||
| Status: | CLOSED ERRATA | QA Contact: | Corey Welton <cwelton> | ||||
| Severity: | medium | Docs Contact: | |||||
| Priority: | unspecified | ||||||
| Version: | 6.0.6 | CC: | adahms, ahuchcha, bbuckingham, bkearney, cwelton, dirk.deimeke, ehelms, jonathan.moore, mhrivnak, mmccune, nshaik, pmutha, sauchter, smane, sthirugn, tcarlin, xdmoon | ||||
| Target Milestone: | Unspecified | Keywords: | FutureFeature, Triaged | ||||
| Target Release: | Unused | ||||||
| Hardware: | Unspecified | ||||||
| OS: | Unspecified | ||||||
| URL: | http://projects.theforeman.org/issues/6637 | ||||||
| Whiteboard: | Verified in Upstream | ||||||
| Fixed In Version: | Doc Type: | Enhancement | |||||
| Doc Text: |
With this release, users of Red Hat Satellite 6.2 can sync down repositories protected by basic authentication by providing the username and password in the repository string.
|
Story Points: | --- | ||||
| Clone Of: | |||||||
| : | 1281611 (view as bug list) | Environment: | |||||
| Last Closed: | 2016-07-27 09:12:16 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: | 260381, 1171330, 1175448, 1281611, 1317008 | ||||||
| Attachments: |
|
||||||
|
Description
Thom Carlin
2014-12-16 20:13:45 UTC
Since this issue was entered in Red Hat Bugzilla, the release flag has been set to ? to ensure that it is properly evaluated for this release. I tested this with pulp 2.5.0 on centos7, and I was able to sync a yum repo. I made a small yum repo on a local machine, used apache to enforce basic auth, and put those credentials in the feed url. $ pulp-admin rpm repo create --repo-id=foo --feed="http://me:letmein@myhost/foo/" I suggest testing this with sat 6.1, and it may just work. The Katello project added this support a few months back (http://projects.theforeman.org/issues/6637) and it should be available in the upcoming 6.1 release. As Michael said, I would suggest testing this out and closing this bug if it indeed works for you. Upstream bug assigned to jsherril Moving to POST since upstream bug http://projects.theforeman.org/issues/6637 has been closed ------------- Justin Sherrill Applied in changeset commit:katello|a1c597d1ce5883d1b99d45551c81b4077e560ae7. No longer onsite at Alcoa, so unable to test. In the future (pulp 2.7+), pulp will accept a username and password as config option for the repo, so you won't need to put them in the URL. https://pulp.plan.io/issues/163 *** Bug 1266499 has been marked as a duplicate of this bug. *** *** Bug 1201986 has been marked as a duplicate of this bug. *** *** This bug is verified in upstream. This fix should eventually land in future downstream builds *** Version Tested: # rpm -qa | grep foreman tfm-rubygem-foreman_discovery-4.1.2-1.fm1_11.el7.noarch tfm-rubygem-foreman_hooks-0.3.9-1.el7.noarch foreman-debug-1.11.0-0.develop.201512111432git98f6ca5.el7.noarch tfm-rubygem-hammer_cli_foreman_docker-0.0.3-4.el7.noarch foreman-ovirt-1.11.0-0.develop.201512111432git98f6ca5.el7.noarch foreman-postgresql-1.11.0-0.develop.201512111432git98f6ca5.el7.noarch foreman-release-scl-1-1.el7.x86_64 foreman-vmware-1.11.0-0.develop.201512111432git98f6ca5.el7.noarch tfm-rubygem-foreman_gutterball-0.0.1-3.el7.noarch foreman-gce-1.11.0-0.develop.201512111432git98f6ca5.el7.noarch dell-per300-01.rhts.eng.bos.redhat.com-foreman-proxy-client-1.0-1.noarch foreman-release-1.11.0-0.develop.201512111432git98f6ca5.el7.noarch tfm-rubygem-hammer_cli_foreman_tasks-0.0.8-1.el7.noarch foreman-1.11.0-0.develop.201512111432git98f6ca5.el7.noarch tfm-rubygem-foreman_docker-1.4.1-2.fm1_10.el7.noarch foreman-libvirt-1.11.0-0.develop.201512111432git98f6ca5.el7.noarch dell-per300-01.rhts.eng.bos.redhat.com-foreman-client-1.0-1.noarch dell-per300-01.rhts.eng.bos.redhat.com-foreman-proxy-1.0-2.noarch tfm-rubygem-hammer_cli_foreman-0.4.0-1.201512101420git81ec371.el7.noarch foreman-compute-1.11.0-0.develop.201512111432git98f6ca5.el7.noarch tfm-rubygem-foreman-tasks-0.7.6-1.fm1_10.el7.noarch foreman-selinux-1.11.0-0.develop.201510071426git6234447.el7.noarch tfm-rubygem-hammer_cli_foreman_bootdisk-0.1.3-3.el7.noarch tfm-rubygem-foreman_bootdisk-6.0.0-2.fm1_10.el7.noarch foreman-proxy-1.11.0-0.develop.201512101505git62c9e22.el7.noarch steps: 1. Create a new repo with URL of form: "https://user:password@host/path_to_file 2. 3. Repository saved screenshot attached Created attachment 1107054 [details]
password protected repo url
*** Bug 1278520 has been marked as a duplicate of this bug. *** Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHBA-2016:1501 |