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.

when trying to sync a mirror repo like:

http://mirrorlist.centos.org/?release=7&arch=x86_64&repo=os&infra=stock

get params are specified.  Katello interprets these as sles auth tokens:  https://github.com/Katello/katello/blob/master/app/services/katello/pulp3/repository/yum.rb#L20-L25

but in this case they are not.  This doesn't actually cause a problem, as usually they are ignored, except its not exactly 100% correct, and exposed another bug in pulp:  https://pulp.plan.io/issues/8816

Created from redmine issue https://projects.theforeman.org/issues/32660

Upstream bug assigned to None

Moving to POST as upstream PR is merged.

To reproduce this issue, try to sync http://mirrorlist.centos.org/?release=7&arch=x86_64&repo=os&infra=stock

Before the change, this sync would have issues as the query string would be interpreted as a SLES auth token. 

With this change, there is now an explicit field for the SLES auth token.

Additionally, verification should include attempting to sync from a SLES repository with a valid auth token supplied either at repo creation in Satellite or by editing an existing repository and specifying the auth token in the repository details page.

Satellite no longer supports SLES so no need to verify this bug.