Artifactory

Administration module | Artifactory

General: Settings, Property Sets, HTTP Settings
Services: Backups, Maven Indexer
Security: Anonymous access, Revoke API Keys, SSH Server, Signing Keys Trusted Keys, Certificated

Xray

Xray Permissions

Administration module | Identity and Access | Permissions

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:

• Manage Components is now  Manage Xray Metadata

• View Components is now included in the Read permission

As part of the permission migration process:

• Users/Groups with Xray Admin and Artifactory Admin permissions will be converted to Administrators in the JFrog Platform. 
• Users/Groups with only Xray Admin permissions will be converted to have Read, Manage, Manage Policies and Manage Watch permissions on all the resources.

For more information, see JFrog Platform Permission Migration.

Administration module | Identity and Access | Users

Administration module | Identity and Access | Groups

• Manage Policies and Manage Watches are now a global permissions that are enabled on the user or group level. Previously this was a permission option in the permission target.
• View Watches is now integrated with the Manage Watches global permission. It is not available as a separate permission.

Application module  | Security & Compliance 

• Watch resources scope of repositories, builds and Release Bundles can be set by name or by Exclude/Include Patterns.
• Manually invoking a re-scan of a watch will apply on all resources defined in the watch. Previously you could set the re-scan on part of the resources.

Administration module | Xray

General: Indexed Resources, Database Sync, Webhooks, Integrations
Advanced: System Parameters and Queue Workers, Xray System Messages, etc.

• When setting the indexed resources scope of repositories, builds and Release Bundles you now set by name or by Exclude/Include Patterns.

• JFrog Xray supports indexing and scanning of Release Bundles as well as defining Watches and Policies on Release Bundles. You can apply a policy on a Watch containing a Block Release Bundle Distribution action to prevent distributing a Release Bundle to edge nodes if it meets a security or License policy defined in JFrog Xray. For more information, see Xray Scanning of Release Bundles.

Mission Control

Services

Administration module | Platform Deployments | Services

Administration module | Monitoring | Service Status

Mission Control Site Explorer

Application module | Dashboard | Topology

Mission Control Insight 

Application module | Dashboard | Trends

Distribution

Artifactory

• Artifactory Homepage: will be available in later JFrog Platform releases. For Mission Control installations, administrators can use the Topology page.

• Native Tree Browser (from UI): The Artifactory native tree browser allows browsing the contents of a repository in a plain html structured tree.
  This will not be available via the new UI. The old URL will still be available for clients who are relying on the tree browser. 

Mission Control

• Projects 

• Notifications

• Disaster Recovery

Artifactory

• License Control is deprecated. Its functionality is included in the Xray integration and provides richer information and support for additional package types.

• Stash Search Results: allowing you to save your search results and go back to them later, has been removed.

• User Plugins: Now is a good time to check the READMEs of any user plugins you got from our User Plugins GitHub to ensure they are still valid and relevant.  All non-deprecated plugins should now work with Artifactory 7.x. If you wrote a custom user plugin that relies on a non-public API you should test it in Artifactory 7.x before deploying to production.

• AJP Connector has been removed and will no longer work, HTTP should be used as an alternative.

Xray

• Out of the box integrations: Aqua, WhiteSource and Black Duck, out of the box integrations are deprecated in the Xray UI integrations page. 
  However, custom integrations are still available, supporting integrating to any external source of your choice. The VulnDB integration, now transparently integrated into Xray, provides the industry's most comprehensive security vulnerability database. This eliminates the need for these out of the box 3rd party integrations.

• Xray Homepage: as part of the JFrog Platform UI unification, this page has been removed.

Mission Control

• Scripts are deprecated in favour of using the CLI.
• Disaster Recovery is deprecated. 

System Architecture

• Artifactory and Xray Pairing: When upgrading to the JFrog Platform, Xray must be connected only to a single Artifactory instance. If you have a single Xray instance connected to multiple Artifactory instances, before upgrading Artifactory and Xray, you will need to split your Xray instance to multiple instances to support this requirement. See details here.
• Artifactory and Distribution Pairing: The upgrade to the JFrog Platform requires mapping a source Artifactory to a single Distribution service. If you are creating and distributing release bundles from multiple source Artifactory instances and one Distribution instance, you will now need to deploy a Distribution service in every JPD that contains these source Artifactory instances. If your Mission Control instance is part of another JPD, you'll need to register it in the new Distribution instance. See details here.
• Oracle database: Working with an Oracle database requires a new driver and setup. See details here.
• MongoDB database, used by Xray prior to the Platform, is no longer needed (except during the data migration). If you are upgrading to the new JFrog Platform, your data will be automatically migrated over to PostgreSQL as part of the upgrade process.
• Inter-product communication
• Custom logback and Sumo Logic Integration

System Directories

• Directory structure: has been updated for all JFrog products to create a standardized structure.
• HA: HA installations with a shared NFS that mount the $ARTIFACTORY_HOME/data directory should now mount the $JFROG_HOME/artifactory/var/data/artifactory directory.
• Logs structure has been updated from version 6.x, additional logs for new microservices have been added, log names have been changed to be aligned with all products and log output format has been changed to be aligned with all products.
  • Log file names are now prefixed by the service name and a dash. For example, the Artifactory log file name has been changed from application.log to artifactory-service.log.
  • Additional logs are now included for the new Router, Metadata, and Frontend.

System Configuration

• Authentication Provider: You no longer configure an Artifactory as an Authentication Provider for Authentication as the new JFrog Platform architecture is based on a join-key method that automatically connects between the JPD and its services.
  For more information, see System Architecture.
• Accessing the UI: The JFrog Platform web UI is now accessed through port 8082 (For example, http://SERVER_HOSTNAME:8082/ui/). Accessing Artifactory directly for REST API and downloads is still possible through port 8081. For more information, see System Requirements.
• Reverse Proxy: The reverse proxy configuration should only be configured for the JFrog Platform, where previously it was configured for each JFrog Product separately. You will need to create a new reverse proxy configuration.
• Load balancer health check endpoint: has been changed from api/system/ping to /router/api/v1/system/ping. See instructions here.
• Using a Custom Context Path for OAuth or SAML SSO Authentication Providers: You will receive an error from your Identity Provider, if you have configured OAuth or your SAML SSO authentication providers, in versions prior to Artifactory 7.x, with the following settings:
  • Your Artifactory Context path was set using a custom context path, for example, mycompany.com/mycompany_test. To preserve this configuration, set the following system property, artifactory.override.context.path as your custom context path.
  • You are using an empty context path, for example: mycompany.com/. To continue using the emtpy context path configuration, set the following system property artifactory.override.context.path=Empty in the artifactory.system.properties file.

JFrog Artifactory

• Replicator: All configurations have been moved from the replicator.yaml to the Artifacotry system.yaml file. See details here.

• Viewing Packages/Builds/Release Bundles: The UI will only load only up to 100 results and up to 100 versions per package/builds/Release Bundle.
• User Plugins: All Artifactory user plugins have been modified and must be updated to their latest version, when upgrading to Artifactory version 7.x. This is due to the file structure change that is introduced in this new Platform version. For example, haAwareEtcDir has been updated to etcDir. See GitHub changes.
• Artifactory as Root Application in Tomcat: Artifactory can no longer be configured as the Tomcat root application. To remove the /artifactory context, you'll need to set the relevant configuration in your reverse proxy (load-balancer). See details here.
• Artifact search via UI/API: By default, the artifact search in Artifactory is set to case-insensitive. This can be modified by applying this system property:

  artifactory.ui.search.artifacts.caseInsensitive=false.

JFrog Xray

• Component Search: searching for components that are not artifacts in your Artifactory instance, but are known to Xray as a result of its recursive scan capability. This functionality will be available in later JFrog Platform releases.
• Xray Permissions
  • The Manage Watch permission is now available as a global permission on the user/group level. Previously manage watches was an option per permission target that was defined with a scope of resources. Now, users/groups with the Manage Watch permission will enable permissions for all resources. When upgrading to the JFrog Platform, the permission conversion will remove the Manage Watch permission for all users and groups. After upgrading, this permission will need to be reconfigured for all required users and groups. Defining a scope will be available in later JFrog Platform releases, as part of the Projects functionality.
  • The View Watches permission is deprecated. To view watches, enable the Manage Watches permission option for users/groups.

Artifactory

• SECURITY
  • Create or Replace Permission Target

Xray

• AUTHENTICATION
  • Get Token
• USER MANAGEMENT
  • Create User
  • Update User
  • Delete User
• BINARY MANAGERS
  • Add Binary Manager 
  • Update Binary Manager 
  • Delete Binary Manager
• LICENSE REPORTS
  • Generate License Report
  • Get License Report
  • Get License Report Components
• SECURITY REPORTS
  • Generate Security Report
  • Get Security Report
  • Get Top Vulnerabilities Security Report
• GRAFEAS
  • Get Note
  • Update Note
  • Create Note
  • Delete Note
  • Get Occurrences by Note ID
  • Get Occurrences by Component ID
• SYSTEM
  • External Ping Request
• PERMISSIONS
  • Get Permissions
  • Get Permission Details
  • Create Permission
  • Delete Permission

• GENERAL SETTINGS
  • Ignore Xray Alert

Distribution

• XRAY
  • Triggers Xray Release Bundle Version Indexing

• RELEASE BUNDLES
  • Create Release Bundle Version
  • Update Release Bundle Version
  • Distribute Release Bundle Version
• PERMISSION MANAGEMENT
  • Create/Update Destinations Permissions by Name
  • Get All Destination Permissions
  • Get Permission by name Distribution
  • Delete Permission by name