[PUP-4470] Puppet's http connection factory doesn't support authenticating proxies - Puppet Jira Server

XML

Word

Printable

Details

Type: Bug
Status: Resolved
Priority: Normal
Resolution: Fixed
Affects Version/s: None
Fix Version/s: PUP 5.5.17, PUP 6.4.4, PUP 6.8.0
Component/s: None
Labels:
- resolved-issue-added

Epic Link:
Agent HTTP
Team:
Coremunity
Story Points:
2
Sprint:
Platform Core KANBAN

Release Notes:
Bug Fix
Release Notes Summary:

Hide
Puppet agents could not connect via an authenticating HTTP proxy when making REST requests to puppet infrastructure, such as when requesting a catalog. Now puppet agents will observe the http_proxy_user and http_proxy_password settings or HTTP_PROXY_USER/PASSWORD environment variables when making those requests.

Show
Puppet agents could not connect via an authenticating HTTP proxy when making REST requests to puppet infrastructure, such as when requesting a catalog. Now puppet agents will observe the http_proxy_user and http_proxy_password settings or HTTP_PROXY_USER/PASSWORD environment variables when making those requests.

Description

Work for ticket ~~PUP-4030~~ uncovered that puppet's http connection code does not support authenticating proxies (that require a username and password). Note there are http_proxy_user and http_proxy_password settings, but they are only used with the PMT and some providers.

Puppet connection handling should be refactored to use Puppet::Util::HttpProxy class.

Attachments

Issue Links

relates to

PUP-4030 Add support for no_proxy env var

Closed

Activity

People

Assignee:: Josh Cooper

Reporter:: Josh Cooper

Votes:: 2 Vote for this issue

Watchers:: 3 Start watching this issue

Dates

Created:: 2015/04/28 11:52 AM

Updated:: 2019/09/16 11:58 AM

Resolved:: 2019/08/14 8:19 AM