How many types of Proxy Settings are present with the Red Hat Satellite 6
Types of Proxy Settings
- There are majorly 3 proxy settings that can be set on the Red Hat Satellite 6 server based on the environment and usage.
- HTTP Proxy for Subscription Manager (these proxy settings apply to the RHEL system where Satellite is running, not to Satellite itself)
- HTTP Proxy
- Content Default HTTP Proxy
HTTP Proxy for Subscription Manager
Note: Settings done to
/etc/rhsm/rhsm.confapply to Satellite's underlying RHEL 7 operating system only and do not affect the Satellite application in any way.
-
This proxy is mentioned under the file
/etc/rhsm/rhsm.conf. This proxy on rhsm.conf will cascade to the yum repo configurations and will allow Red Hat Satellite Server to get registered to the Red Hat Customer Portal. -
The proxy information can be added in the subscription-manager configuration file in
/etc/rhsm/rhsm.confmanually with the following options:an http proxy server to use proxy_hostname = port for http proxy server proxy_port =
-
The following fields are also required when using an authenticated proxy:
# user name for authenticating to an http proxy, if needed proxy_user = # password for basic http proxy auth, if needed proxy_password =
HTTP Proxy
-
Sets a proxy for outgoing connections from Red Hat Satellite to capsules and other API calls, to internal Satellite services, for example. Not used to sync content.
-
The Proxy can be set on the Red Hat Satellite on the path:
Administer >> Settings >> General >> HTTP(S) proxy -
The HTTP Proxy can also be set using the hammer commands:
# hammer settings set --name=http_proxy --value=Proxy_URL
Content Default HTTP Proxy
-
The
Content Default HTTP Proxyis to be used not only for content synchronization (Pulp2 and Pulp3) which is directly related to Repository sync but also to communicate with the upstream consumer (customer portal), such as refreshing manifest on the Red Hat Satellite 6. -
This content default http proxy will take precedence over the
HTTP proxy(Administer >> Settings >> General >> HTTP(S) proxy). -
If the Content default http proxy is not set, then only Satellite will use the
HTTP proxy(Administer >> Settings >> General >> HTTP(S) proxy) to connect to the upstream consumer. -
These repositories can be Red Hat Repositories or any Custom Repositories.
-
The Proxy can be set on the Red Hat Satellite on the path:
Administer >> Settings >> Content >> Default HTTP Proxy
The Content Default HTTP Proxy can also be set using the hammer commands:
-
Add a Content Default HTTP proxy entry to Satellite:
# hammer http-proxy create --name=myproxy --url http://myproxy.example.com:<Port-no> --username=proxy_username --password=proxy_password -
Configure Satellite to use this Content HTTP proxy by default:
# hammer settings set --name=content_default_http_proxy --value=myproxy