Using the latest JFrog products?
JFrog Platform User Guide
JFrog Mission Control 3.x Documentation
To get the latest version, go to the JFrog Unified Platform
Proxies are configured on the site level in the Config Proxy page. Services located on the site are automatically allocated the site proxy.
To view the list of proxies configured, in the Admin module, select Proxy | Config Proxy.
To create a new proxy, click Add Proxy and specify the basic site settings and credentials.
A logical name for this proxy
The proxy URL.
Note: A URL associated with a service should not be used as a proxy URL.
A user name required to access the proxy server (optional).
The password required to access the proxy server (optional).
- Click Add Site Pair and select the source and target sites to pair.
Configuring an NTLM Proxy
Mission Control supports several types of network proxies including NTLMv2. When running on Linux, you may want to use NTLMv2 with CNTLM.
NTLM Authorization Proxy Server (APS) is a proxy software that allows you to authenticate via a Microsoft Proxy Server using the proprietary NTLM protocol.
NTLM is supported by running an ad-hoc CNTLM container like https://hub.docker.com/r/robertdebock/docker-cntlm/.
Configure an NTLM Proxy
Run the container to hash the NTML credentials.
The following output is generated:
Run the container with the hashed credentials.
In Mission Control, create a proxy in the Admin module, select Proxy | Config Proxy with the following parameters.
Note that the credentials are not required because they are handled by CNTLM.
From Mission Control 3.2, proxies previously configured on the Service level are automatically migrated to the Site level. Proxies configured in Mission Control enable communication between services and are now dependent on the site on which the service is located. During Mission Control startup proxy configuration is automatically migrated to reflect the right Site pair based according to the following rules:
- The proxy on the source sites is automatically set as the Mission Control site. Initially, it is set with the default Site (MC_Site) that can later be changed in the Admin section to the valid site.
- If a service uses a proxy and has a site, the proxy site pair will refer to the Mission Control site as the source and service site as the destination.
- If no proxy is required to connect to a service, the service will be assigned by default to the Mission Control site.
- If a service uses a proxy and doesn't have a site, a new site may be created and assigned to the service and the proxy Site pair has Mission Control Site as source and Service's Site as the destination.
- If a proxy has been configured, but not associated with any service, the configuration will remain as is.
Sites created as a part of migration can be updated at any time on the Service level or in the Admin section.
Mission Control supports managing Proxies through the REST API.