Need help with other JFrog products?

JFrog Enterprise+
JFrog Artifactory
JFrog Xray
JFrog Distribution
[JFrog Pipelines]
JFrog Bintray
JFrog Access

Using the latest JFrog Mission Control version? See the documentation here.

Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 118 Next »


This page presents release notes for JFrog Mission Control describing the main fixes and enhancements made to each version as it is released.


Click to download the latest version of JFrog Mission Control.


For installation instructions please refer to Installing Mission Control

To upgrade to the latest version, please refer to Upgrading Mission Control

(lightbulb) To receive automatic notifications whenever there is a new release of Mission Control, please watch us on Bintray.

Mission Control 3.5

Released: March 20, 2019


License Management Improvements

This release introduces the ability to split a single bucket into any number of separate buckets that can be applied to multiple environments as needed.

Additionally, to allow you to easily scale your Artifactory cluster up/down, you can now attach any number of licenses to multiple services. 

Support Bundle Improvements

From this version, you can easily create support bundles for multiple services managed by a Mission Control with a single REST API. Using the Create Platform Support Bundle REST API, each support bundle will be created and saved in the jfrog-support-bundle repository of the Authentication Provider.

Certificate Management

Mission Control now allows you to upload self signed certificates to communicate with SSL enabled services. The newly introduced trusted certificate REST API will automatically propagate the certificates to all microservices.

Feature Enhancements

Enterprise Authentication Provider Improvements

For Enterprise+ customers, Mission Control will automatically upgrade your Authentication Provider with an Enterprise+ license.

Elasticsearch HA Architecture

Mission Control now supports an internal Elasticsearch Cluster architecture, and Elasticsearch version 6.6.

Issues Resolved

  1. Fixed an issue with creating an Access Federation Mesh topology.

  2. Added Log rotate support for insight server logs.

  3. Allow configuring connection timeouts for gathering Artifactory metrics. 
  4. Removed usage of non secure cookie during Single Sign-on callback.

Mission Control 3.5.1

Released: April 3, 2019 

Issues Resolved

  1. Fixed an issue with upgrading from versions 3.0.0 - 3.2.1 to 3.5.0 for RPM/DEB installations. 
  2. Fixed an issue with calls to Artifactory storage summary API.

Mission Control 3.5.2

Released: April 16, 2019 


Access Federation Mesh Topology Improvements

Mission Control now supports adding filters for user permissions within a Mesh Topology in Access Federation. This requires all selected Artifactory services to be version > 6.2.

Project Insights Dashboard Improvements

Project dashboard UI rendering performance has been improved to load the graphs faster.

Support bundle API

The Create Support bundle REST API has been enhanced to track the Support bundle creation and return a response only once completed. 

Issues Resolved

  1. Fixed an issue whereby querying Artifactory build data for Project Insights has been optimized.
  2. Fixed a security issue to remove the TRACE method.
  3. Fixed an issue with the Storage summary showing incorrect data for Cache size.
  4. Fixed the installer to allow passing custom Java options.

Mission Control 3.5.3

Released: May 31, 2019 

Issues Resolved

  1. Fixed an issue in Access Federation to trigger full sync when a topology is configured or updated.
  2. Fixed security vulnerabilities in one of the Mission Control dependencies.
  3. Fixed an issue with Support Bundle API to synchronously trigger the Support Bundle creation and return a status. 
  4. Added a flag to disable monitoring of Edge nodes.
Page Contents

Mission Control 3.4

Released: January 17, 2019

Deprecated Version Warning

The Mission Control 3.4.0 version has been deprecated and will no longer be available to download.

This is due to an issue related to the mc.key file, that was fixed in the latest 3.4.1 version.

Mission Control 3.4.1

Released: January 23, 2019


MongoDB Replaced with a Relational Database

To lower the overhead when installing and upgrading Mission Control, Mission Control 3.4 has replaced its use of MongoDB with PostgreSQL. This will also facilitate the support of additional relational database in the future. 

Feature Enhancements

Mission Control High Availability

JFrog Mission Control 3.4 introduces a highly available active-active cluster architecture, central management and monitoring your services. ensuring continuous security and governance to your software packages. This feature is available from Enterprise license onwards.  

Java 11 Compatibility

Java 11 compatibility has been added to Mission Control, as Java 8 support end of life is coming up, and Mission Control contains components that require Java to run properly and include Java runtime as part of the Mission Control.

Hardened Security for Secrets

To harden security when providing encrypted data (secrets) such as connection strings to external databases, from this version, when running Mission Control, you can optionally provide secrets in a temporary file. Mission Control will load the parameters specified in a temporary secrets file, located in jfmc.secrets.location, at startup and then delete the file. Notice that this is an additional recommended functionality that will not change your current behavior if not used.

MBeans is Deprecated 

From Mission Control 3.4, MBeans has been deprecated.

Issues Resolved

  1. Resolved an issue with cronjob. The rpm/deb installer now also adds a cronjob that runs every 2 minutes. The cronjob triggers a script which validates that mission-control is running as expected and in case of errors, attempts to restart the services.

  2. Resolved an issue whereby Mission Control Docker services restarted only on failure exit code.

  3. Resolved an issue whereby a white label error page is displayed at times when attempting to log in using SSO.

  4. Resolved an issue whereby the `latitude` and `longitude` coordinates were not detected in the Sites table.

  5. Resolved an issue whereby reindexing an index with big size is timing out after 30000 ms when upgrading Elasticsearch.

  6. Resolved an installation issue in relation to writing temporary files in Docker Compose.

  7. Resolved an issue whereby a Mission Control account was locked due to multiple POST requests.

Mission Control 3.4.2

Released: January 30, 2019


Offline Bucket

In addition to using a signed URL and connecting to JFrog Bintray, you can now upload your license buckets to JFrog Mission Control using an offline bucket file. This saves the need for Mission Control to connect to Bintray, enabling an easy configuration for users with Mission Control configured behind a firewall.

License buckets can be uploaded from the Mission Control UI and using REST API

Docker Offline Installation

JFrog Mission Control can now be installed using a Docker offline installation.

Issues Resolved

  1. Resolved an issue where Access Federation setup failed due to the Artifactory service ID format change.
  2. Support for ElasticSearch credentials and certificates. For ElasticSearch OSS, credentials can be enabled using the Search Guard plugin. 

  3. Support for ElasticSearch 6.3.

Mission Control 3.4.3

Released: March 11, 2019 

Issues Resolved

  1. Fixed an issue with the Mission Control SSL configuration.
  2. Fixed an issue with permissions for custom UID or GID for the Mission Control Docker Compose.
  3. Fixed an issue with HA node recovery, where in some cases successfully recovered nodes were not available in the cluster.

Mission Control 3.3

Released: November 6, 2018

Feature Enhancements

Access Federation API

Mission Control now provides a set of dedicated Access Federation APIs that allow you to set, get, and modify access federation configurations on the service level or for all services. 

Installation Enhancements

Manual Mission Control Installation 

You can now manually install Mission Control without scripts for Debian and RPM.

Installing Mission Control Using Docker Compose

From Mission 3.3, you can install Mission Control as a new installation using Docker Compose allowing you to orchestrate your setup using Docker Compose. This will ensure you have all the required services specified in a single JSON file with pre-configured parameters.

Zip Installation Enhancements

The following enhancements have been made to the Zip installation:

  • The Mission Control services only require the read/write permission on MongoDB instead of the dbOwner.
  • Parameterized all MongoDB databases allow users to change the names.
  • Seeding external MongoDB database runs smoothly.

Issues Resolved

  1. Fixed an issue whereby Birthday attacks against TLS ciphers with 64bit block size vulnerability (Sweet32).
  2. Fixed an issue whereby Certs created for internal communication need to be high-grade CIPHERS.
  3. Fixed issues regarding scripts by adding the capability to add or remove existing attributes and create input type USERxxxx.
  4. Fixed an issue whereby you could not upgrade Artifactory with valid licenses to E+ bucket licenses.
  5. Fixed an issue whereby the build number was not displayed intermittently.
  6. Fixed an issue whereby the date and time were incorrectly displayed in Mission Control for Disaster Recovery.
  7. Fixed a Disaster Recovery issue whereby Artifactory Config Descriptor is larger than 16MB. 

Mission Control 3.3.1

Released: December 12, 2018

Issues Resolved

  1. Fixed an issue in which disaster recovery would fail quietly at the DR - Synchronize step if the names of the remote repository on the master and of the local repository on the target are the same.
  2. Added support for custom UID or GID for the Mission Control Docker Compose ElasticSearch image. 
  3. Added a REST API endpoint to get all buckets
  4. Fixed an issue with displaying Enterprise buckets to choose when adding/editing Service  

Mission Control 3.3.2

Released: December 13, 2018 

Issues Resolved

  1. Fixed an issue with support for custom UID or GID for the Mission Control Docker Compose Elasticsearch image. 

Mission Control 3.2

Released: October 10, 2018


Proxy Management

Proxy management is now simplified as admins can configure and manage proxies on the Site level instead of configuring a proxy for each individual Service. This enables the right proxy to be selected based on the Site on which the Service is located. Proxy settings from previous versions are automatically migrated to reflect the existing Site pairing and the Onboarding Wizard has been modified to accommodate the need to configure a proxy for Mission Control.


Insight Projects now allows you to drill down into the build/run allowing users to see consolidated data from all the tools connected to the Project in one single location. The dashboard layout has also been enhanced to enable showing more details. 

Service Trends

From 3.2, Service Trends has replaced the Graphs tab. You can now view a set of dedicated trends and specific data related to the JFrog services including storage and usage, vulnerabilities, and distributions. 

Support Bundles

As part of the JFrog SLA based support, you can now collect Mission Control logs in a support bundle using REST API. The logs will be pushed to Mission Control Authentication provider Artifactory and will be available for download or upload to the JFrog support site.

Feature Enhancements

Access Federation

Access Federation has been simplified allowing you to select entity types per connection instead of per source. The wizard now lets you specify the target only for the single direction sync setup.

Xray Service Page

You can now view the Repository scan % and Build Info scan % statistics for the Xray service.

Docker installation

Mission Control Docker users no longer need root access to the Container.

Conda Support

Mission Control scripts now support Conda package type.

Issues Resolved

  • Fixed an issue whereby Mission Control incorrectly identified Artifactory licenses.
  • Fixed an issue whereby the health check generated an error message.
  • Fixed an issue related to parsing during the upgrade process.
  • Fixed an issue regarding filtering in the Artifactory service page.
  • Fixed an issue whereby after upgrading from Mission Control 2.1.1, the CentOS rpm elasticsearch 5.6.2, with the  “/var/lib/elasticsearch” data folder changed to Mission Control 3.0.1 in CentOS rpm elasticsearch 6.1.1. The data folder is now set by default to “/usr/share/elasticsearch”.
  • Fixed an issue with the script editor.
  • Fixed an issue related to the support rebind authentication provider.
  • Fixed an issue related to script dry-run.

Mission Control 3.2.1

Released: March 8, 2019

Issues Resolved

  1. Added a new configuration parameter to control timeout for connecting to JFrog Artifactory, for high latency environments.

Mission Control 3.1

Released: July 2, 2018



Installing Mission Control has been made easier with the availability of generic installers for RPM based systems (CentOS and Red Hat) and Debian based systems (Debian and Ubuntu). In addition, a ZIP installation is now also available for all LINUX flavors supported by Mission Control. For updates to the installation process, please refer to Installing Mission Control.   

Access Federation

Setting up access federation has a new UI making this process easier than ever.  

Elasticsearch Clusters

Mission Control now supports Elasticsearch clusters to support scaling up while maintaining performance. 

Insight with Projects

Mission Control projects have been enhanced and now allow extraction of data from multiple services or builds to give insights over a wider range of services at a time including both upstream and downstream Jenkins jobs. In addition, insights can now also be obtained over any custom time range that contains data. A project can provide insights from up to 25 builds, and you can select up to 10 builds to display in the dashboard.

Feature Enhancements

Scripting with Edge Nodes

Artifactory Edge nodes can now be provided to Mission Control configuration scripts as user input by specifying "EDGE" as the user input type in Mission Control scripts.

Replication in Star Topology Scripts

The script template that sets up a Star Topology has been enhanced to include replication blocks that let you configure the parameters that govern the replication between the Artifactory services in the star topologies.

Issues Resolved

  1. Fixed an issue which prevented Mission Control License Bucket management from issuing an Enterprise+ license from a bucket to a single Artifactory service if that service already had an expired license or an Enterprise license. 
  2. Fixed an issue in which when setting up Access Federation, if any of the synchronization targets returned a conflict, synchronization of security entities to other targets would cease. Following this fix, synchronization of security entities will resume and complete successfully for all targets that do not return a conflict.
  3. Fixed an issue which caused Mission Control installation to fail if JAVA_HOME could not be found. In this case, Mission Control will now prompt the user to enter JAVA_HOME.
  4. Fixed an issue in which Mission Control could not find JAVA_HOME on CentOS installations unless it was symlinked in /usr/bin

Mission Control 3.1.2

Released: August 21, 2018


Previous versions of JFrog Mission Control presented an issue with the implementation of Disaster Recover for Artifactory services (6.1 and 6.2) in which security settings (users, groups and permissions) were not properly DR protected. This release of Mission Control, together with the release of JFrog Artifactory 6.3 solves this issue with the following enhancements:

Enhanced Disaster Recovery 

Mission Control's management of Disaster Recovery has been enhanced to use  JFrog Access service in order to allow security entities (users, groups and permissions) to be synchronized from a Master Artifactory service to its corresponding Target service. Need to configure Circle of Trust functionality between Master and Target services. 

Compatibility with Artifactory 6.3 for Disaster Recovery

This patch release of Mission Control fully supports DR for Artifactory 6.3 and above. If you are using Artifactory 6.1 or 6.2 and want to implement DR for your Artifactory services, you need to upgrade to Artifactory 6.3. Note however, that if you do not wish to implement DR, you may upgrade to this release of Mission Control without having to upgrade your Artifactory services. 

Issues Resolved

  1. Fixed an issue in which you could not change the description of an Artifactory remote repository using a configuration script.
  2. Fixed an issue in which, when running on Ubuntu, if connectivity to MongoDB was disrupted, certain REST API calls would fail.
  3. Fixed an issue in which certain URLs used to specify the Mission Control Git repository used to manage configuration scripts would be considered invalid.
  4. Fixed an issue in which certain parameters in a NuGet repository configuration script were removed even though they were not specified in the script.
  5. Fixed an issue which prevented graphs from being displayed when Mission Control was run in Chrome v68.

Mission Control 3.0

Released: May 17, 2018 


JFrog Enterprise+

Announcing the new Enterprise+ Platform, that provides a complete solution for covering all the steps involved in creating a secure, trustworthy, and traceable software release in a multi-site development environment.

The solution works in conjunction with source version control, continuous integration, and deployment tools.

The JFrog Enterprise+ platform bundle includes:

  • JFrog Artifactory: all features available with an Enterprise license as well as Access Federation and the ability to work with Artifactory Edge.
  • JFrog Distribution: an on-premise, centralized platform that lets you provision software release distribution.
  • JFrog Xray: universal analysis of binary software components at any stage of the application lifecycle providing unprecedented visibility into issues lurking in components anywhere in your organization.
  • JFrog Mission Control: all features available in Mission Control with the addition of: 

    • the ability to add instances of Jenkins-CI, JFrog Distribution and JFrog Artifactory Edge as services in the system and monitor them

    • Insight and analytics on build processes through as set of metrics on the end to end build process

Mission Control Enterprise+ Dedicated Features

The following dedicated Enterprise+ features are a part of the Mission Control 3.0 release:

  • Gain Insight into Projects: Projects provide insight into your release process through a set of metrics generated from various tools including Jenkins and Artifactory. A Project can be a single microservice or a complete application and is defined using a set of builds in Artifactory. Project resources are automatically discovered from the different tools, and the data is collected and refreshed periodically resulting in a set of metrics that visualize the release process in the Project dashboard.

  • Enterprise+ Dedicated Services:

    • Edge: JFrog Artifactory Edge (an "Edge node") service is an edition of JFrog Artifactory whose available features have been customized to serve the primary purpose of distributing software. For more information, see Edge Service.
    • Distribution: The Distribution service manages Release Bundles and their distribution processes, including release content, permission levels, and target destinations. For more information, see Distribution Service.

    • Jenkins: The Jenkins service collects information on your builds in Jenkins and extends the view you gain in the Enterprise+ Projects Dashboard by integrating Jenkins as part of your build process in the CI/CD process. For more information, see Jenkins Service. 

  • Managing Access Federation in Mission Control: Access Federation gives you control over access to all, or any subset of your global JFrog Artifactory, JFrog Xray, and JFrog Distribution services from one location by synchronizing all security entities (users, groups, permissions and access tokens) between the federated services. Once access federation has been set up, you can manage all security entities in the federated services from one place. For more information, see Managing Access Federation.
    Access Federation is initially configured through a YAML configuration file that is uploaded to the different access Services, and the results are displayed in Mission Control in the Admin module/ Access Federation/ Configuration page. For more information, see Access Federation.

Get Started Quickly with Mission Control Onboarding Wizard 

When accessing Mission Control for the first time or when doing an upgrade from Mission Control 2.x version, Mission Control launches the Onboarding Wizard that lets you go through the basic setup and configuration so you can get started immediately. The Onboarding Wizard lets you reset the admin password, create a site, add license buckets and configure the Authentication Provider. For more information, see Mission Control Onboarding Wizard.

Permission Management

From version 3.0, JFrog Mission Control offers a granular permissions model that provides Mission Control administrator ability to grant permission to users and groups on different resources in Mission Control. The resources include services, scripts, and projects (E+ feature). Mission Control does not keep local users and groups but assigns permissions to users and groups located on an Artifactory service configured as an Authentication Provider. For more information, see Permissions.


From Mission Control version 3.0, user management in Mission Control has been greatly simplified. By adding the ability to authenticate Mission Control users through your corporate  Artifactory service. All you need to do is define a leading Artifactory service as an "Authentication Provider" in the Mission Control Onboarding Wizard.  For more information, see Authentication.

Added Single Sign-on Support (SSO)

SSO allows you to log into all your JFrog applications using a single set of user credentials that are stored in the Authentication Provider Artifactory instance. When SSO is applied, the user logs into the JFrog product using a set of predefined credentials and is granted access across the board to the JFrog products. SSO eliminates the need to re-enter the credentials every time a product is accessed. It is automatically enabled for all the JFrog services that use an Authentication Provider for managing security. For more information, see Authentication Using Single Sign-On

Script Execution

From Mission Control 3.0, you can apply permissions to scripts. The Mission Control admin can create scripts and configure the VCS together with the ability to grant the Execute Script permission to users. 

Feature Enhancements

Generate Tokens for API Calls

Prior to running Mission Control REST API calls you need to generate an access token. The token is valid for 60 minutes. 

Database upgrades

Supports Elasticsearch version 6.1 

Non-interactive mode for Mission Control installer 

Following customer requests for an automated process for installing Mission Control, we have added to option to use default parameters when performing installations and upgrades. 

The clean Installation:

  • Sets a default data folder location.

  • Uses internal databases (not custom databases).

  • When SELinux is enforced, the mongo policy package is installed without requiring user confirmation. 

The upgrade process: 

  • Skips the step whereby the user is required to confirm whether to proceed with the upgrade.

  • Uses the same configuration for folder locations and databases.

Issues Resolved

  1. Removed PHP dependencies.

  2. Docker log enhancements including fixing issues and adding log rotation for mission-control docker microservice.

  3. API v1 and v2 were deprecated in Mission Control 2.x and are now deleted in Mission Control 3.0.

Mission Control 3.0.1

Released: May 28, 2018

Issues Resolved

  1. Fixed a critical issue relating to JFMC installations on different Unix flavors. 
  2. Fixed an issue in which the Jenkins registration and authentication failed. 
  3. Fixed an issue in which encryption is randomly not working in Go packages. To learn more, see  Unable to Decrypt Go Packages.

Mission Control 3.0.2

Released: June 26, 2018

Issues Resolved

Fixed an issue connected to user or group names containing the "dot" (".") character. 

For a Mission Control installation, click to download this latest version of  JFrog Mission Control.

Mission Control 2.1

Released: January 8, 2018


Ubuntu and Red Hat Installation 

This release introduces support for additional flavors of Linux and adds Ubuntu 16.x and and Red Hat 7.x as supported platforms. For details on how to install Mission Control on these platforms, please refer to Installing Mission Control. . 

Using External Databases

Mission Control uses Elasticsearch, MongoDB and PostgreSQL databases for its different functions, and until now, would install dedicated instances of each of these databases. This version gives you more control of your resources and lets you direct Mission Control to use instances of these databases you may already have installed and in use, rather than creating new ones. Offering full flexibility, during the installation or upgrade process, Mission Control lets you select which databases should externalized and which Mission Control should create for its own dedicated use.

Maven Metadata in DR Repositories Tab 

In addition to the replication status, for Maven packages, the DR Repositories tab now also includes the metadata file count and size for each repository.

System Monitoring

Mission Control now displays your general system status as an icon on the top ribbon of the UI. Services notifications are automatically updated at all times. 

Feature Enhancements

  1. In both the UI and the REST API, the option to execute a script on a non-online service is blocked. 
  2. JFrog Mission Control blocks creating a DR pair when the master version is higher than target version. 
  3. In the REST API, two new commands have been added. The Change Password command allows users to change their own password and enables the admin to change passwords for all users. The Partial Update Site By Name command updates site information without updating the attributes.
  4. When setting DR, you can manually set the replication socket timeout in the DR configuration properties file.
  5. Mission Control allows you to add a commit message when updating a script.
  6. The Top 5 Services graph now displays the percentage of used storage. 


Mission Control 2.1.1

Released: January 23, 2018


Helm Chart Repositories

This release adds full support in Mission Control for Helm Chart repositories which were introduced in JFrog Artifactory 5.8. 

Mission Control 2.0

Released: November 20, 2017

JFrog is pleased to release Mission Control 2.0.

This release introduces many changes from version 1.x to improve workflow and efficiency in managing your global Artifactory and Xray services. Yes, you read correctly, Mission Control now also manages your Xray services. In addition, Mission Control 2.0 introduces significant changes in installation and upgrade procedure, workflow for adding and managing services, a new concept of Sites that associate services to a geographic location, improvements in Usage Graphs and more. 

Note that some of the new features and enhancements are breaking changes that are not compatible with version 1.x. In these cases, we offer a migration path to version 2.0. 

For details about the changes introduced by Mission Control 2.0, please read the sections below.


Artifactory and Xray Services

In addition to managing your Enterprise Artifactory instances, Mission Control can now also manage the JFrog Xray instances attached to them. This allows you to do things like configure connections between Artifactory and Xray services, use scripts to create Watches and more.  

To manage Artifactory or Xray instances through Mission Control, they must be added as Services and be assigned to Sites.


Scripting has undergone significant changes in Mission Control 2.0. Most importantly, configuration scripts are now much more flexible allowing you to operate on as many Artifactory or Xray services, and on any number of repositories as you want in a single script (previously, each script could only perform one action on a single service). To support this capability, Mission Control 2.0 introduces service closures in configuration scripts. These define the Artifactory and Xray instances on which the script operates and enclose the different configuration blocks that create or implement changes on Artifactory and Xray services.

The scripting DSL has also been significantly enhanced with new configuration blocks. These include configuration blocks to create and configure Xray services, a security block to configure users, groups and permissions in Artifactory services and more. Make sure to check out the Star Topology configuration blocks that make it very easy to set up a complex one-to-many replication relationship using three lines of code. Not also that applying a Star Topology configuration to all members of a star actually implements a full mesh topology.

Breaking Change - You need to migrate your scripts

The new scripting mechanism is a breaking change which means that scripts written for JFrog Mission Control 1.x will not work in version 2.0 and above. While there is no way to migrate your scripts automatically, the process is not very complicated. For guidelines and best practices for migrating your scripts please refer to Migrating Scripts from Version 1.x to Version 2.x.


The Graphs UI has been enhanced to give you an easy way to focus on different Artifactory instances and repositories and also zoom in on specific time periods on historical usage graphs. From version 2.0, Mission Control uses a new Elasticsearch database to store historical usage data. Upon installation of the new version, the previous InfluxDB database will no longer be used, and usage data will only be collected in the new database. 

[Optional] You may migrate historical usage data from InfluxDB to Elastic Search

If you wish to continue viewing historical usage data collected in the InfluxDB database of versions 1.x, you can migrate this data to the new Elasticsearch database using the process described in Migrating Scripts from Version 1.x to Version 2.x.

Installation and Upgrade

Instructions for installing and upgrading to version 2.0 have changed, but remain simple procedures, with support for CentOS, Debian and Docker installations. 

To install Mission Control 2.0 as CentOS or Debian distribution, please refer to Installing Mission Control

To install and run the Mission Control Docker image, please refer to Running with Docker

ZIP installation is deprecated

From version 2.0, Mission Control is no longer available as a ZIP installation.


Mission Control 2.0 introduces a completely new REST API that accommodates all the new functionality introduced in this version. The new REST API adds several new endpoints, but also removes some, including endpoints related to configuring users, groups and permissions in Artifactory since this functionality is now available through JFMC scripting. From Mission Control 2.0, the REST API v3 is active, while the REST API v2 is deprecated. 

Breaking Change - You need to migrate your REST API calls

The new REST API is a breaking change which means any scripts that use the previous REST API version will not work. To learn how to migrate your scripts to the new REST API, please refer to Version Mappings in the new Mission Control REST API page.


Sites are a new concept in JFrog Mission Control. They represent physical locations (cities) into which you can aggregate the different Artifactory and Xray services serving them. Any service defined in Mission Control must be assigned to a site. Sites are displayed in the Explore module (which replaces the old Dashboard module) and can display sites as a list view or on a map. 

Existing Artifactory services are automatically assigned to a site

When you upgrade to Mission Control 2.0, any Artifactory services already managed by your current version of Mission Control will be assigned to new Sites that will be created according to the location of your Artifactory instances. For example, an Artifactory service located in San Fransisco, will be assigned to a new site in Mission Control that's located in San Fransisco.

Artifactory services that do not have a location will be placed in the "Unassigned Services" site by default.

"Groups" feature is deprecated

From version 2.0, collecting managed Artifactory services into "Groups" is deprecated. All services should be placed in the context of a Site.

Feature Enhancements

  1. Mission Control startup time has been greatly improved.
  2. Mission Control's DSL has been enhanced with new configuration blocks to allow extremely easy configuration of replication relationships that implement Star Topologies for geographically distant Artifactory services. starPush configures a multi-push replication relationship while starPull configures pull replication. As a result, the multipushReplication configuration block, which is now redundant, has been deprecated. 
  3. The Execute Script REST API endpoint has been enhanced to provide more detailed error messages if script execution fails

Issues Resolved

  1. Fixed an issue that prevented Mission Control from implementing DR when the Master Artifactory instance was using encrypted passwords.

Mission Control 1.12

Released: August 9, 2017

Feature Enhancements

  1. To support TLS/SSL authentication between two Artifactory instances for replication, a new field, clientTlsCertificate, has been added to the Replication and Multi-push replication DSL blocks.
  2. To support disabling the indexing of filelist.xml metadata file in RPM repositories, a new field, enableFileListsIndexing, has been added to the Local Repository DSL block.  
  3. Artifactory instances that use one of the supported cloud storage providers will no longer appear in the Top 5 Instances graph since their storage capacity is effectively infinite.
  4. In addition to being able to display the top 5 repositories for all managed instances, in the Top 5 Repositories graph you can now select a specific Artifactory instance and display the top 5 repositories for that instance

Mission Control 1.11

Released: June 2, 2017



The Mission Control Graphs module has been updated to include a Storage and Artifact Usage graph showing the amount of storage used and number of artifacts. It allows you to get an overall view of all Artifactory instances (and their repositories) managed by Mission Control, or to focus on a specific instance and repository. This graph supports Predictions, and when enabled, it will also estimate how these figures will grow over time 3, 6, 12 and 24 months into the future.

The "Top 5 Instances (Historical)" and "Top 5 Repositories (Historical)" graphs have been removed. 

Feature Enhancements

  1. You can now use the REST API to run a script on a group of instances. Previously this was only available through the UI.
  2. You can now trigger replication of a repository directly from the Monitor module in the Mission Control UI.
  3. When "webapp" is part of Artifactory's root URL, JFMC now removes it when it issuing a system "ping" request.
  4. You can now disable predictive analysis for graphs that support it (currently only the Storage / Artiafct Usage graph). When disabled the time scale stops at "Now" and you cannot scroll the graph to view future dates. 

Issues Resolved

  1. Fixed an issue that prevented updating YUM repositories in instances of Artifactory 5.x.
  2. Fixed an issue in which importing the repository configuration for an RPM repository resulted in a configuration script that incorrectly specified the package type as "Generic". With this fix, the package type is now correct (RPM).
  3. Fixed an issue in which, during startup, the Mission Control service would return a response of 200 OK to a REST API call even though it was unable to carry out the request. In this scenario, Mission Control now returns "503 Service Unavailable Error".
  4. Fixed an issue in which caused connectivity problems between Mission Control and the influxDB database under certain circumstances.

Mission Control 1.10

Released: April 3, 2017

InfluxDB Log Rotation 

To prevent the InfluxDB log files from becoming inflated, Mission Control now manages them automatically using log rotationLog rotation is currently supported for RPM and Debian installations. 

Refreshing Mission Control Extensions

The Mission Control extensions used to reconnect to Artifactory instances have been enhanced. After upgrading to this version, make sure you upload the updated extensions to Artifactory as described in Reconnecting to Managed Instances

Main Updates
  1. If a replication is configured with an invalid cron expression, an exception is written to the output logs. Mission Control will continue to try parsing the next replication status and will only return the valid replications in the response.
  2. Mission Control now supports DR sync for custom repository layouts named with a "-default" suffix such as "mycustom-default".
  3. Mission Control Instance Storage Summary now displays additional information, including storage used by Cached FS and Sharding binary providers.

Mission Control 1.10.1

Released: May 14, 2017

Issues Resolved

  1. Fixed an issue that caused replication from the Master to a non-DR instance to fail during the DR Init phase.

Mission Control 1.9

Released: February 21, 2017

Compatibility with Artifactory

This release updates Mission Control to support the latest features released with Artifactory 5.1

Configuration Management with Chef and Puppet at Global Scale

This release of Mission Control complements new features in Artifactory 5.1 by adding support for Chef and Puppet. This provides administrators with central control, management and monitoring of Chef Cookbook and Puppet repositories across all of an organizations’ worldwide Artifactory instances.

Main Updates
  1. Mission Control now supports Chef Cookbook and Puppet repositories in Artifactory.  
  2. Mission Control now displays the artifact count for both the source and target repositories in the Monitor module Replication tab
  3. The time to load the replication relationships, in the Replication tab, has been reduced. 
  4. DR performance has been improved by ensuring that the Master instance's configuration script will only be pushed to the Target instance if it has been modified.
  5. When performing DR, Mission Control will only check available space when the target instance storage is configured with a filesystem binary provider.
  6. An issue with sending a test email when configuring the mail setup for notifications, has been fixed.

Mission Control 1.8

Released: February 13, 2017

Compatibility with Artifactory

This release updates Mission Control to support the latest features released with Artifactory 5.0. 

Cluster License Management

This release of Mission Control complements new features in Artifactory 5.0 by adding support for Artifactory's Cluster License Manager for HA installations. 

Main Updates
  1. An issue preventing DR Initialization due to incorrect calculation of storage required on the DR instance has been fixed.
  2. An issue preventing DR Initialization because availability of cloud storage, such as S3, on the DR instance not being detected, has been fixed.
  3. If you access JFrog Mission Control while it is still starting up, you will now see a cool startup animation rather than getting 404.
  4. The defalt value for snapshotVersionBehavior in the localRepository block DSL has been corrected to show "unique" as the default value.
  5. Configuration scripts managed on a Git repository may now be accessed via SSH, in which case you do not need to provide a User Name and Password 
  6. An issue preventing Mission Control from connecting to InfluxDB after the hosting server is awakened from sleep mode has been fixed.
  7. In this version, Mission Control adds support for deploying licenses to Artifactory 5 HA clusters that manage licensing internally using Artifactory's Cluster License Manager

Mission Control 1.7

Released: December 28, 2016

Storage Based Event Notifications

Mission Control launches event notifications by email. By configuring a set of policies on managed instances and repositories, Mission Control will send email alerts based on specific events. Currently, events connected to storage are supported, so you can get email alerts when an instances free space passes the set percentage threshold, or when a repository's used space passes the set usage threshold.

Predictive Graphs

Mission Control Graphs have been enhanced to show not only historical data, but also predictive data. Now, you don't have to second guess how your instances and repositories will behave in the future. Mission Control runs a predictive analysis and displays an estimation of how your instances and repositories will use storage 3, 6, 12 and 24 months into the future.

Main Updates

In addition to UI enhancements and many bug fixes, this release includes the following main updates: 

  1. Configure Mission Control to send email notifications for storage based events. 
  2. Mission Control Graphs now show predictive analysis.  
  3. Disaster Recovery now supports both remote and virtual repositories (in addition to local repositories that were previously supported).
  4. When attaching a license from a license bucket using JFrog CLI, the bucket_id parameter can take either the bucket name or the bucket ID.
  5. You now have the option of deleting DR replication configurations once a DR Target instance has completed being restored to the Master, or when deleting a Master/Target pair.  
  6. Mission Control performance related to sending ping requests to a newly instantiated Artifactory instance has been greatly improved.
  7. Mission Control now supports Smart Remote Repositories.
  8. When entering user input to specify the package type in a configuration script, the possible values are now selected from a drop list

Mission Control 1.7.1

Released: January 25, 2017

Main Updates
  1. This patch fixes an issue related to changing DR replication status during the synchronization process in DR Init phase.

Mission Control 1.6

Released: November 16, 2016

New Installation

Mission Control standalone installations for Windows, Mac and Linux now come in separate ZIP files. 

Docker Upgrade

Mission Control Docker upgrade has been greatly simplified and uses an installation script. 


Mission Control displays Graphs showing historical data on Artifactory instances and repositories giving you a view to past usage and insights on trending behavior. This is supported by an InfluxDB database which is now included in all variants of Mission Control installation files.

Main Updates

In addition to above main enhancements and bug fixes, this release includes the following updates: 

  1. An issue that caused Mission Control to lock a user when registering an instance with a plain text password has been fixed.
  2. If any node in a cluster has a duplicate or disabled license, the whole cluster will be disabled.
  3. Support for PHP Composer repositories has been added.

Mission Control 1.6.1

Released: December 14, 2016

Conan Repositories

Mission Control takes centralized global repository management to the world of C/C++ development. With the addition of support for Conan in the latest release of JFrog Artifactory, v4.15, Mission Control is fully aligned and also supports Conan repositories for C/C++ binary components. 

Main Updates

In addition to UI enhancements and many bug fixes, this release includes the following main updates: 

  1. Add support for Conan repositories.

Mission Control 1.5

Released: September 27, 2016

Disaster Recovery

Several enhancements have been made to Disaster Recovery:

  • A variety of instance configuration files are backed up in DR. These include repository layouts, property sets, proxies, LDAP and LDAP Group settings and SSO configuration.
  • A REST API endpoint to match up DR master and target pairs has been added 
  • Before initializing DR, Mission Control verifies that there is enough storage available on the target instance
Git Integration
  • Previously, only configuration scripts that complied with certain limitations on the script name could be managed on Git. This limitation has now been removed.
  • Pulling scripts from branches is now supported
  • Anonymous users on the Git repository are now supported

JMX MBeans can also monitor changes in an Artifactory's instance state (started up, or went down)

Docker Installation

Mission Control Docker installation has been greatly simplified and uses an installation script.

Main Updates

In addition to UI enhancements and many bug fixes, this release includes the following main updates: 

  1. Enhanced Disaster Recovery
  2. Improvements to the Git integration
  3. JMX MBeans that monitor Artifactory state
  4. Improved Docker installation script
  5. Issues with the license and the plugin have been fixed
  6. Issues with the EULA and Docker pull have been fixed

Mission Control 1.5.1

Released: October 20, 2016

PHP Composer Repositories

This version supports PHP Composer repositories introduced in Artifactory v4.14.0

Main Updates
  1. Support PHP Composer local and remote repositories.

Mission Control 1.5.2

Released: November 2, 2016

Disaster Recovery
  • DR at Scale: Disaster Recovery has been tested with large repositories holding terabytes of data to ensure coherent DR and recovery on a large scale.
  • Artifact Stats: When configuring DR, you can specify that Mission Control should replicate artifact statistics. This will prevent artifacts from inadvertently getting removed by user plugins that perform cleanup based on artifact statistics such as "Last Downloaded" or "Number of Downloads".
  • User Plugins: User plugins are now also DR protected which means they are copied over to the target instance in a DR situation, and copied back to the master instance in recovery.
Download Blocking

Repository configuration scripts have been enhanced to include the blockXrayUnscannedArtifacts and xrayMinimumBlockedSeverity parameters that control download blocking in Artifactory.

Main Updates
  1. Artifact statistics and user plugins are now DR protected.
  2. Repository configuration scripts now include download blocking parameters.

Mission Control 1.4

Released: August 8, 2016


Monitor a variety of parameters using any JMX agent.

Git Integration

Manage configuration scripts in a Git repository.

Script Validation

Get instant feedback from Mission Control on validity of your configuration scripts

Docker Installation

Mission Control is now available as a Docker image

Main Updates

In addition to UI enhancements and many bug fixes, this release includes the following main updates: 

  1. Monitoring with MBeans  
  2. Git Integration 
  3. Script Validation 
  4. New security templates for configuration scripts 
  5. Mission Control Docker installation 

Mission Control 1.3

Released: July 3, 2016

Disaster Recovery

JFrog Mission Control now offers one-click disaster recovery for your Artifactory instances. Once DR is configured, in case of any event that makes one of your Artifactory installations inoperable, you may resume operations almost immediately at the click of a button in Mission Control. Users of the downed instance may not even notice that anything happened.


JFrog Mission Control REST API has been upgraded to v2. This version is significantly changed from v1 of the REST API which is now deprecated, and we strongly recommend that you upgrade your scripts to use the new API.

Mission Control Backup

Mission Control can manage backup and disaster recovery for Artifactory, but what happens if the server on which you're running Mission Control itself goes down? To support this scenario, and facilitate nearly instant recovery, Mission Control may now be easily backed itself up to facilitate near-real-time recovery.

Main Updates

In addition to UI enhancements and many bug fixes, this release includes the following main updates: 

  1. Setting up Disaster Recovery for Artifactory 
  2. REST API v2
  3. Mission Control Backup facilities 

Mission Control 1.2

Released: May 20, 2016

License Bucket Management

JFrog Mission Control introduces License Bucket management which automates, and therefore, greatly simplifies the management of licenses for large numbers of Artifactory instances.

Main Updates

In addition to UI enhancements and many bug fixes, this release includes the following main updates: 

  1. License Bucket Management

Mission Control 1.1

Released: February 28, 2016

Debian Installation

Mission Control is now available for installation as a Debian distribution

Main Updates

In addition to UI enhancements and many bug fixes, this release includes the following main updates: 

  1. Installation as a Debian distribution

Mission Control 1.0

Released: February 1, 2016

JFrog is proud to announce the release of JFrog Mission Control 1.0. This version follows several weeks of customer testing and implements many of the requests provided in the feedback we received on our preview version.


Mission Control's monitoring capabilities have been greatly enhanced and allow its operator to view a variety of information about managed Artifactory instances. These include JVM parameters, storage summary, replication data and running Artifactory tasks.

Environment Setup

To facilitate quick, repeatable and accurate setup of Artifactory instances, Mission Control now offers the capability to import configuration parameters from existing Artifactory instances, tweak them as necessary, and then deploy them to other Artifactory instances. This presents a quick and easy way to provision uniform configuration to any number of Artifactory instances.


Mission Control now exposes a rich REST API to allow fully automated management of Artifactory instances including creating and updating instances, creating and updating repositories, creating and updating users, groups and permissions, all through REST API.


Mission Control now provides convenient wizard-based license management. Easily deploy licenses to all your Artifactory instances in a single bulk operation and be alerted of duplicate licenses that you may have in your global Artifactory network.

Main Updates

In addition to UI enhancements and many bug fixes, this release includes the following main updates: 

  1. Greatly enhanced Monitoring module providing extensive information about the JVM, storage, replication and tasks of managed Artifactory instances.
  2. Importing configurations
  3. REST API.  
  4. Managing Artifactory licenses
  5. Enhanced Dashboard with geo-location map.
  • No labels