Features and Functionality
The user interface provides a consistent experience across all JFrog products. It is designed to support the most commonly used workflows, including improved package management, security and compliance, and package distribution, continuing to provide you with full flexibility. To support this experience the internal architecture (defined as a JPD) is designed to provide JFrog users with the same user experience across the JFrog products that have been installed.
To support the different user workflows, the UI is divided into two main modules:
Application Module providing an easy to use interface for viewing your packages, builds and artifacts in Artifactory. Including Xray security vulnerabilities and violations, Dashboard topology and trends, Distribution release bundles and Pipelines DevOps automation.
- Administration Module providing a consolidated place for configurations of all JFrog products (common and product specific). Including centralized settings, such as monitoring (storage, replication, service status), security and compliance, proxies, license and user management. As well as, property sets, backups, indexed resources, database sync and webhooks.
Both modules include an advanced search mechanism.
Flexible Permissions Model
Administrators get fine-grained permissions control over how users and groups access the different resources (repositories, builds, Release Bundles, destinations).
Security and Compliance Across your DevOps Pipeline
Fully integrated into the JFrog Platform, JFrog Xray protects your artifacts, repositories, builds and release bundles across the entire CI/CD pipeline.
- Get JFrog's vulnerability database that is continuously updated with new component vulnerability data. Including VulnDB, the industry's most comprehensive security vulnerability database.
- Identify security vulnerabilities and license violations according to your organization's needs. A dedicated Security and Compliance section in the UI allows you to set policies and watches on all your JFrog resources.
- Configure watches and policies with the option to block artifact download, Release Bundle distribution to Edge nodes, and even break Builds.
- Use advanced filtering that allows you to configure include /exclude patterns when setting indexed resources or when setting a Watch on the resources.
The JFrog platform installation/upgrade includes the following highlights:
- Common system directory structure for the product application and variables (configurations, data and log)
- Flexible System YAML Configuration Files enabling easy automation
- Alignment of all installers user experience and compatibility matrix
Secure Distribution Process
Manage the creation and distribution of Release Bundles to your Artifactory Edge Nodes. Gain better visibility and traceability into your distribution process with a complete view of all contents and package references of your Release Bundles.
The following table is a quick reference to common functionalities in the JFrog Platform, including their new locations and any functional changes.
Location in the New UI
|Custom Base URL|
Look and Feel Settings
|Dedicated Artifactory Settings|
General: Settings, Property Sets, HTTP Settings
As part of the JFrog Platform permissions unification, permission targets that were previously separated per product are now represented as one permission target with multiple permission options for the different JFrog products. Changes include:
As part of the permission migration process:
For more information, see JFrog Platform Permission Migration.
|Policies and Watches|
|Dedicated Xray Settings|
General: Indexed Resources, Database Sync, Webhooks, Integrations
|Release Bundles are scanned by Xray|
|License and Licence Buckets||Consolidated Licenses for all the JFrog products.|
Mission Control Site Explorer
|Dashboard displays JPD topology.|
Mission Control Insight
|Distributable and Received Release Bundles|
The following table describes features that are currently under development and will be available in later JFrog Platform releases.
Not available in the initial JFrog Platform release.
|Internet Explorer||The Internet Explorer browser is not supported in the JFrog Platform. For a list of supported browsers, see Browsers.|
Prior to Upgrading to the JFrog Platform
When upgrading to Artifactory version 7.x from a previous major version (e.g. 6.x), all other associated JFrog services must be upgraded to these compatible versions:
Artifactory 7.x will not work with any previous major versions of these services.
Additionally, none of these new versions of Mission Control(4.x), Xray(3.x), or Distribution(2.x) will be compatible with Artifactory 6.x.
Do you have more than one Artifactory instances connected to your single Xray instance?
When upgrading to the JFrog Platform, Xray must be connected only to a single Artifactory instance. If you have one Xray instance connected to more than one Artifactory instances, use one of the following options before proceeding with any upgrade:
Option 1 (recommended): Keep one connected Artifactory instance to your single Xray instance, and upgrade the rest to version 7.x with newly installed Xray version 3.x instances. This option will require re-indexing the additional Artifactory instances, and will cause some loss of configuration data. Learn More >
Option 2: Install additional Xray version 2.x instances for each Artifactory instance that you have, and restore all MongoDB and PostgreSQL data. Continue to upgrade each Artifactory and Xray pairs to version 7.x and version 3.x. This procedure is only suggested if you must keep all your Xray configurations and easily reconfigure them in the new instances. Learn More >
REST API Changes
New shared base url for all JFrog services
The JFrog Platform release introduces a new unified way to access all JFrog services, with the exception of Artifactory, using a single
port, using the following format:
JFrog Artifactory will continue to work as before,
The REST API documentation for all JFrog products has been updated to use the new shared base url.
Note: For backward compatibility, each JFrog product will continue to have its own server_url and port.
The following table summarizes the list of changes from previous JFrog products versions to the JFrog Platform.