Uploaded image for project: 'Puppet'
  1. Puppet
  2. PUP-4470

Puppet's http connection factory doesn't support authenticating proxies

    Details

    • 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

            Activity

              People

              • Assignee:
                josh Josh Cooper
                Reporter:
                josh Josh Cooper
              • Votes:
                2 Vote for this issue
                Watchers:
                3 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved:

                  Zendesk Support