Bug 1566517 - Error while refreshing manifest " Error refreshing manifest. bad component(expected userinfo component or user component): DOMAIN\user " when AD integrated proxy server is used.
Summary: Error while refreshing manifest " Error refreshing manifest. bad component(ex...
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Subscription Management
Version: 6.2.13
Hardware: x86_64
OS: Linux
medium with 1 vote vote
Target Milestone: Unspecified
Assignee: satellite6-bugs
QA Contact: jcallaha
Depends On:
TreeView+ depends on / blocked
Reported: 2018-04-12 12:57 UTC by Ashish Humbe
Modified: 2020-06-09 17:18 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Last Closed: 2019-12-03 12:53:11 UTC
Target Upstream Version:

Attachments (Terms of Use)

Description Ashish Humbe 2018-04-12 12:57:27 UTC
Description of problem:

On a satellite server (6.2 and 6.3) which has a proxy server configured that is integrated with windows AD server, while refreshing the manifest it fails with below error: 

Error refreshing manifest. bad component(expected userinfo component or user component): DOMAIN\user

Version-Release number of selected component (if applicable):
Satellite v 6.2 and 6.3

How reproducible:
Always when using an authenticated proxy server with AD user

Steps to Reproduce:
1. Take/setup a squid proxy server which is integrated with AD.
2. Configure the proxy details on the satellite server

# satellite-installer --scenario satellite --katello-proxy-url= --katello-proxy-port=3128 --katello-proxy-username='DOMAIN\user' --katello-proxy-password='secret'

3. Try to refresh the manifest on the satellite server

Actual results:

Manifest Refresh fails with "Error refreshing manifest. bad component(expected userinfo component or user component): DOMAIN\user" error.

Expected results:

Manifest refresh should work successfully 

Additional info:

Comment 3 Ben Formosa 2018-07-27 00:55:39 UTC
I've had this same issue with Satellite 6.3.2

The backslash in the username causes Pulp's JSON parser to fail.

# journalctl -xe --unit=pulp_resource_manager.service
pulp.server.initialization:ERROR: One or more plugins failed to initialize. If a new type has been added, run pulp-manage-db to load the type into the dat
celery.worker:ERROR: (42273-47840) Unrecoverable error: ValueError('Invalid \\escape: line 6 column 34 (char 119)',)

Satellite should support usernames and passwords with special characters.
See also:

The installer could url-encode them before writing to configuration files.

Additionally, anything that reads the proxy configuration should support url-encoded usernames and passwords.

There's an issue open on rest-client addressing this: https://github.com/rest-client/rest-client/issues/661

I can't find an issue in Pulp, but I believe it will have the same issue.
The JSON configuration file is read here:

The username and password is handed to the requests module here:

Requests configuration:

Comment 4 Bryan Kearney 2019-11-04 14:33:50 UTC
The Satellite Team is attempting to provide an accurate backlog of bugzilla requests which we feel will be resolved in the next few releases. We do not believe this bugzilla will meet that criteria, and have plans to close it out in 1 month. This is not a reflection on the validity of the request, but a reflection of the many priorities for the product. If you have any concerns about this, feel free to contact Red Hat Technical Support or your account team. If we do not hear from you, we will close this bug out. Thank you.

Comment 5 Bryan Kearney 2019-12-03 12:53:11 UTC
Thank you for your interest in Satellite 6. We have evaluated this request, and while we recognize that it is a valid request, we do not expect this to be implemented in the product in the foreseeable future. This is due to other priorities for the product, and not a reflection on the request itself. We are therefore closing this out as WONTFIX. If you have any concerns about this, please do not reopen. Instead, feel free to contact Red Hat Technical Support. Thank you.

Note You need to log in before you can comment on or make changes to this bug.