Red Hat Bugzilla – Bug 1180637
katello-installer use character "\" in proxy-username option
Last modified: 2018-09-19 11:20:07 EDT
Description of problem: When I attempt to use a "\" character in the option --proxy-username for katello-installer, it is not recognizing the "\" correctly. I am required to to use a proxy server to access the internet. The username resides in Active Directory. I have confirmed that the username and password allow me to access the internet via YUM and successfully accesses the Redhat repos. The username follows the windows convention of "domain\username". My katello-installer command is as follows. katello-installer --katello-proxy-url=http://proxy.url/ --katello-proxy-port="port" --katello-proxy-username="domain\username" --katello-proxy-password="password" The above command completes successfully but I see "407, authentication required" errors in the log files. When I execute a katello-installer --help, the value for the proxy-username option shows this: --katello-proxy-username Proxy username for authentication (default: "domain\\username") Version-Release number of selected component (if applicable): Additional info: When trying to use the @ it gives a 407 error. RHSM proxy works with the \ symbol Customer is using this proxy info: ----------------------------------------------------------------------- The authentication is via Active Directory through the Cisco Context Directory Agent. The following may or may not be of interest: Model: S370 Version: 7.7.0-753 for Web Configuration Summary Security Services Web Proxy Web Proxy: Enabled Web Proxy Mode: Transparent IP Spoofing: Not Enabled HTTPS Proxy: Enabled Native FTP Proxy: Enabled SOCKS Proxy: Disabled L4 Traffic Monitor L4 Traffic Monitor Enabled L4 Traffic Monitor Action: Block Services Acceptable Use Controls: Enabled Reputation Filtering: Web Reputation: Enabled Adaptive Scanning: Enabled Cisco IronPort Engine: Webroot: Enabled McAfee: Disabled Sophos: Enabled Cisco IronPort Data Security Filters: Enabled SensorBase Network Participation: Disabled ---------------------------------------------------------------------- http://www.cisco.com/c/en/us/support/security/web-security-appliance-s370/model.html
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.
would using single quotes get around the issue?
The Pulp upstream bug status is at NEW. Updating the external tracker on this bug.
The Pulp upstream bug priority is at Normal. Updating the external tracker on this bug.
The Pulp upstream bug status is at ASSIGNED. Updating the external tracker on this bug.
The Pulp upstream bug priority is at High. Updating the external tracker on this bug.
The Pulp upstream bug status is at POST. Updating the external tracker on this bug.
The Pulp upstream bug status is at MODIFIED. Updating the external tracker on this bug.
Upstream is FIXED, ready to be merged.
VERIFIED: -0.3.7-2.el7sat.noarch rubygem-hammer_cli_foreman_docker-0.0.3.10-1.el7sat.noarch foreman-gce-1.7.2.47-1.el7sat.noarch rubygem-hammer_cli_foreman_discovery-0.0.1.10-1.el7sat.noarch hp-bl490cg6-01.rhts.eng.bos.redhat.com-foreman-proxy-1.0-2.noarch foreman-debug-1.7.2.47-1.el7sat.noarch foreman-compute-1.7.2.47-1.el7sat.noarch foreman-vmware-1.7.2.47-1.el7sat.noarch ruby193-rubygem-foreman-redhat_access-0.2.4-1.el7sat.noarch rubygem-hammer_cli_foreman_tasks-0.0.3.5-1.el7sat.noarch ruby193-rubygem-foreman_bootdisk-4.0.2.13-1.el7sat.noarch hp-bl490cg6-01.rhts.eng.bos.redhat.com-foreman-client-1.0-1.noarch hp-bl490cg6-01.rhts.eng.bos.redhat.com-foreman-proxy-client-1.0-1.noarch foreman-ovirt-1.7.2.47-1.el7sat.noarch ruby193-rubygem-foreman_discovery-2.0.0.22-1.el7sat.noarch rubygem-hammer_cli_foreman-0.1.4.14-1.el7sat.noarch foreman-selinux-1.7.2.17-1.el7sat.noarch ruby193-rubygem-foreman_gutterball-0.0.1.9-1.el7sat.noarch foreman-postgresql-1.7.2.47-1.el7sat.noarch ruby193-rubygem-foreman_docker-1.2.0.24-1.el7sat.noarch rubygem-hammer_cli_foreman_bootdisk-0.1.2.7-1.el7sat.noarch foreman-libvirt-1.7.2.47-1.el7sat.noarch foreman-1.7.2.47-1.el7sat.noarch ruby193-rubygem-foreman-tasks-0.6.15.7-1.el7sat.noarch foreman-proxy-1.7.2.6-1.el7sat.noarch steps: # katello-installer --katello-proxy-url=http://go-proxy.fpl.com --katello-proxy-port=8080 --katello-proxy-username=fplnt\admin --katello-proxy-password=changeme -v [ INFO 2015-11-30 04:52:46 verbose] Executing hooks in group post Success! * Katello is running at https://hp-bl490cg6-01.rhts.eng.bos.redhat.com Initial credentials are admin / changeme * Capsule is running at https://hp-bl490cg6-01.rhts.eng.bos.redhat.com:9090 * To install additional capsule on separate machine continue by running: capsule-certs-generate --capsule-fqdn "$CAPSULE" --certs-tar "~/$CAPSULE-certs.tar" The full log is at /var/log/katello-installer/katello-installer.log [ INFO 2015-11-30 04:52:46 verbose] All hooks in group post finished We are able to login using webUI also no errors in log file
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/RHSA-2015:2622
The Pulp upstream bug status is at CLOSED - CURRENTRELEASE. Updating the external tracker on this bug.