Bug 1371662 - [RFE] Add NTLM proxy support to Satellite 6
Summary: [RFE] Add NTLM proxy support to Satellite 6
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Usability
Version: 6.2.0
Hardware: x86_64
OS: Linux
medium
high vote
Target Milestone: Unspecified
Assignee: satellite6-bugs
QA Contact: Katello QA List
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-08-30 18:18 UTC by rakesh kumar
Modified: 2021-06-10 11:33 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2018-09-04 19:09:27 UTC
Target Upstream Version:


Attachments (Terms of Use)

Comment 3 Patrick Toal 2018-05-14 14:58:54 UTC
I have a different customer, also facing this issue.  They use a BlueCoat proxy, and it is configured to require authentication to make outbound connections.  The authentication is NTLM only.

The issue is that pulp can not connect to repos to sync through their proxy without NTLM support.

We are trying a workaround, to whitelist cdn.redhat.com in the proxy, but this is also failing, because their proxy is configured to only allow unauthenticated connections to trusted sites in the browser PKI, which cdn.redhat.com is not.

Comment 4 Bryan Kearney 2018-09-04 18:58:04 UTC
Thank you for your interest in Satellite 6. We have evaluated this request, and we do not expect this to be implemented in the product in the foreseeable future. We are therefore closing this out as WONTFIX. If you have any concerns about this, please feel free to contact Rich Jerrido or Bryan Kearney. Thank you.

Comment 5 Bryan Kearney 2018-09-04 19:09:27 UTC
Thank you for your interest in Satellite 6. We have evaluated this request, and we do not expect this to be implemented in the product in the foreseeable future. We are therefore closing this out as WONTFIX. If you have any concerns about this, please feel free to contact Rich Jerrido or Bryan Kearney. Thank you.


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