Bug 1325001

Summary: [RFE] Allow specifying repository auth credentials as HTTP headers
Product: Red Hat Satellite Reporter: Bruno Rocha <rochacbruno>
Component: RepositoriesAssignee: satellite6-bugs <satellite6-bugs>
Status: CLOSED DUPLICATE QA Contact: Katello QA List <katello-qa-list>
Severity: low Docs Contact:
Priority: unspecified    
Version: 6.2.0CC: bkearney
Target Milestone: Unspecified   
Target Release: Unused   
Hardware: All   
OS: All   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2016-05-11 15:27:00 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:

Description Bruno Rocha 2016-04-07 19:53:02 UTC
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=="

Comment 1 Bryan Kearney 2016-05-11 15:27:00 UTC

*** This bug has been marked as a duplicate of bug 1281611 ***