Need help with other JFrog products?
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.
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.
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.
Resolved an issue whereby Mission Control Docker services restarted only on failure exit code.
Resolved an issue whereby a white label error page is displayed at times when attempting to log in using SSO.
Resolved an issue whereby the `latitude` and `longitude` coordinates were not detected in the Sites table.
Resolved an issue whereby reindexing an index with big size is timing out after 30000 ms when upgrading Elasticsearch.
Resolved an installation issue in relation to writing temporary files in Docker Compose.
Resolved an issue whereby a Mission Control account was locked due to multiple POST requests.
Mission Control 3.4.2
Released: January 30, 2019
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.
Docker Offline Installation
JFrog Mission Control can now be installed using a Docker offline installation.
- Resolved an issue where Access Federation setup failed due to the Artifactory service ID format change.
Support for ElasticSearch credentials and certificates. For ElasticSearch OSS, credentials can be enabled using the Search Guard plugin.
- Support for ElasticSearch 6.3.
Mission Control 3.4.3
Released: March 11, 2019
- Fixed an issue with the Mission Control SSL configuration.
- Fixed an issue with permissions for custom UID or GID for the Mission Control Docker Compose.
- 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
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.
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.
- Fixed an issue whereby Birthday attacks against TLS ciphers with 64bit block size vulnerability (Sweet32).
- Fixed an issue whereby Certs created for internal communication need to be high-grade CIPHERS.
- Fixed issues regarding scripts by adding the capability to add or remove existing attributes and create input type USERxxxx.
- Fixed an issue whereby you could not upgrade Artifactory with valid licenses to E+ bucket licenses.
- Fixed an issue whereby the build number was not displayed intermittently.
- Fixed an issue whereby the date and time were incorrectly displayed in Mission Control for Disaster Recovery.
- Fixed a Disaster Recovery issue whereby Artifactory Config Descriptor is larger than 16MB.
Mission Control 3.3.1
Released: December 12, 2018
- 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.
- Added support for custom UID or GID for the Mission Control Docker Compose ElasticSearch image.
- Added a REST API endpoint to get all buckets.
- Fixed an issue with displaying Enterprise buckets to choose when adding/editing Service
Mission Control 3.3.2
Released: December 13, 2018
- 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 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.
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.
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.
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.
Mission Control Docker users no longer need root access to the Container.
Mission Control scripts now support Conda package type.
- 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
- 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.
Setting up access federation has a new UI making this process easier than ever.
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.
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.
- 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.
- 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.
- 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.
- Fixed an issue in which Mission Control could not find JAVA_HOME on CentOS installations unless it was symlinked in
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.
- Fixed an issue in which you could not change the description of an Artifactory remote repository using a configuration script.
- Fixed an issue in which, when running on Ubuntu, if connectivity to MongoDB was disrupted, certain REST API calls would fail.
- Fixed an issue in which certain URLs used to specify the Mission Control Git repository used to manage configuration scripts would be considered invalid.
- Fixed an issue in which certain parameters in a NuGet repository configuration script were removed even though they were not specified in the script.
- 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
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.
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.
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.
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.
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.
Removed PHP dependencies.
Docker log enhancements including fixing issues and adding log rotation for mission-control docker microservice.
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
- Fixed a critical issue relating to JFMC installations on different Unix flavors.
- Fixed an issue in which the Jenkins registration and authentication failed.
- 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
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.