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.
Description of problem:
Repositories (e.g: fedorapeople.org) allows authentication using the url based basic http auth:
"http://USER:PASS@repo_owner.fedorapeople.org/reponame/"
In the above format, on product -> new repository it is possible to specify credentials that leads to an url of maximum 1024 chars length.
It is not usual to have long USER:PASS, however counting with the size of URL + reponame and specially if special chars are used in credentials.
(eg: username: 䑧㭿䑧㭿䑧㭿䑧㭿䑧㭿䑧㭿䑧㭿䑧㭿䑧㭿䑧㭿䑧㭿䑧㭿䑧㭿䑧㭿 or username: Márçião) each char counts as 4 when quoted.
Example:
>>> url_encode("䑧㭿䑧㭿䑧㭿䑧㭿䑧㭿䑧㭿䑧㭿䑧㭿䑧㭿䑧㭿䑧㭿䑧㭿䑧㭿䑧㭿")
>>> '%E4%91%A7%E3%AD%BF%E4%91%A7%E3%AD%BF%E4%91%A7%E3%AD%BF%E4%91%A7%E3%AD%BF%E4%91%A7%E3%AD%BF%E4%91%A7%E3%AD%BF%E4%91%A7%E3%AD%BF%E4%91%A7%E3%AD%BF%E4%91%A7%E3%AD%BF%E4%91%A7%E3%AD%BF%E4%91%A7%E3%AD%BF%E4%91%A7%E3%AD%BF%E4%91%A7%E3%AD%BF%E4%91%A7%E3%AD%BF'
>>> # 252 chars
So to allow the use of special chars (eg: utf8) in credentials and avoid passing the limit of 1024 chars it would be a great idea to specify custom HTTP headers.
So encoding "username:password" as base64 will allow the use as headers
"Authorization: Basic QWxhZGRpbjpvcGVuIHNlc2FtZQ=="