Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
Red Hat Satellite engineering is moving the tracking of its product development work on Satellite 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 "Satellite project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs will be migrated starting at the end of May. 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 "Satellite project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/SAT-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.
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.
Description of problem:
Unable to use basic authentication in Sat6 Repository
Version-Release number of selected component (if applicable):
6.0.6
How reproducible:
Every time
Steps to Reproduce:
1. Create a new repo with URL of form: "https://user:password@host/path_to_file
2.
3.
Actual results:
"An error occurred saving the Repository: is invalid
Expected results:
Repository x saved
Additional info:
Comment 1RHEL Program Management
2014-12-16 20:24:04 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.
Moving to POST since upstream bug http://projects.theforeman.org/issues/6637 has been closed
-------------
Justin Sherrill
Applied in changeset commit:katello|a1c597d1ce5883d1b99d45551c81b4077e560ae7.
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
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