Released July 12, 2023
API Key Deprecation
As notified in Artifactory 7.47.10, support for API Key is slated to be removed in a future release. To ease customer migration to reference tokens, which replaces API key, we are disabling the ability to create new API keys at the end of Q3 2024. The ability to use API keys will be removed at the end of Q4 2024. For more information, see JFrog API Key Deprecation Process.
Artifactory 7.63.5 is Available as a Cloud and Self-Hosted Version
Artifactory 7.63.5 is the Self-Hosted version and contains all the highlights, feature enhancements, and bug fixes stated in Artifactory 7.63.4 and Artifactory 7.63.2 as part of our Cloud-first initiative.
Known Issue in this Version
under some circumstances, users who attempt to modify their binary-store.xml configuration file might experience files being deleted. Users with Sharding Cluster and Eventual Cluster configured should upgrade to version 7.63.11 or higher. For more information, see Known Issues.
Join Key issue when you upgrade to Artifactory 7.59.9 - 7.63.7
If you used Join Key to register a remote JPD, the Mission Control microservice in the home JPD fails to connect to the remote JPD and the remote JPD appears as offline in the topology after a certain period.
Cause
This issue occurs because the Access microservice in the remote JPD fails to recognize the Mission Control microservice of the home JPD and marks it as a stale service. When the Access cleanup process runs, the join key is revoked.
Result
As a result, you cannot distribute release bundles to the remote JPD, access federation with the remote JPD fails, and affects your license buckets.
Solution
To avoid this issue, you must re-register the remote JPDs that you registered using join keys with Pairing Tokens before you upgrade.
If you upgraded to an affected version, you must re-register the remote JPDs with Pairing Tokens so the remote JPDs are accessible again.
Breaking Change for Artifactory Bootstrap YAML
From Artifactory version 7.58 and forward, the Artifactory Bootstrap YAML no longer contains LDAP (from Artifactory version 7.54), Crowd (from Artifactory version 7.57), or HTTP SSO (from Artifactory version 7.58) authentication provider configuration settings. You can now use the Access Configuration Bootstrap YAML to set up HTTP SSO, LDAP, and Crowd authentication provider configuration for your self-hosted JFrog Platform.
Breaking Change for Global Configuration Descriptor
From Artifactory version 7.59 and later, the Global Configuration Descriptor file no longer contains LDAP, Crowd, or HTTP SSO Authentication Provider Configuration. You can use the Authentication Provider REST API to modify authentication provider configuration. Alternatively, from Artifactory version 7.63 and forward, you can use the Access Configuration Bootstrap YAML to set up authentication provider configuration.
Breaking Change for Docker Installation
Installation of Artifactory 7.55 and later, may not work on versions prior to Docker 20.10.10 because older Docker versions do not support certain changes to the JFrog Products Container Base Image. Previously, Docker installation was supported on Docker version 18 and above. Docker version 18 and 19 are now end of life.
Highlights
Support for OpenShift
Artifactory now supports the installation on OpenShift environment using the artifactory and artifactory-ha Helm Charts. For more information, see Install Artifactory Single Node on OpenShift and Install Artifactory HA on OpenShift.
If you previously used the OpenShift operator to install Artifactory in OpenShift, you can continue to use the operator.
Support for RHEL 9
Artifactory now supports RHEL 9.
Feature enhancements
Split Service Containers in Helm Installation
The value of the splitServicesToContainers attribute is now set as true by default in the artifactory and artifactory-ha Helm Charts installation/upgrade. The different microservices of Artifactory now runs as separate containers in a single pod. For more information about the microservices, see JFrog Artifactory Service.
If you do not wish to have split containers, you can pass a values.yaml file with the splitServicesToContainers attribute is set as false along with the Helm Chart installation/upgrade. Note that the ability to set the attribute as false will be deprecated in a future.
Prune Unreferenced Data Support for Azure
Artifactory now supports the Prune Unreferenced Data storage maintenance operation for providers using Azure, GCP, and S3 storage. Note that since the Prune Unreferenced Data mechanism induces many interactions with remote file storage, this operation may be time-consuming.
Create multiple SSH keys
It is now possible to generate more than one SSH Public Key through the WebUI on the Edit Profile page. For more information, see SSH Key.
Custom Login Dialog
You can now add a custom login dialog that users must accept before they can log into the JFrog Platform. For more information, see Custom Login Dialog.
Enhanced Shard Health Check in Sharding Binary Provider and Sharding Cluster Binary Provider
In this Artifactory version, you can now configure options (balancerThreads, accessibleCheckThreads, and accessibleCheckTimeoutMillis) in the Sharding Binary Provider and Sharding Cluster Binary Provider to check the health of shards and provide stability to a sharded filestore. The logging for the health check of the shards has also improved and now the logs provide warnings for the shards that are not accessible. If you set the logger to debug level, you can see the status of the health check of shards and metrics about the latency check of each shard.
Access Configuration Bootstrap YAML
You can now use the Access Configuration Bootstrap YAML to set up HTTP SSO, LDAP, and Crowd authentication provider configuration for your self-hosted JFrog Platform, instead of the Artifactory Bootstrap YAML.
Authentication Provider Configuration Options
You can use the Authentication Provider REST APIs or the Access Configuration Bootstrap YAML to set up HTTP SSO, LDAP, and Crowd authentication provider configuration. From Artifactory version 7.59 and later, the Global Configuration Descriptor file no longer contains LDAP, Crowd, or HTTP SSO authentication provider settings.
Crowd Authentication REST APIs
You can now use Crowd Authentication REST APIs to configure Crowd authentication provider configuration settings.
Resolved Issues
JIRA Issue | Description |
|---|---|
Fixed an issue that prevented users from deleting a repository that has "-cache" at the end of its name. You can now delete such repositories with the Apply Artifactory YAML Configuration Changes API. | |
RTDEV-33502 | Fixed an issue whereby, when getting the Crowd settings using the Artifactory WebUI, the settings were not fetched correctly. |
RTDEV-30604 | Fixed an issue whereby, users who performed a search in a Conan repository with insufficient permissions could not perform any searches afterward in Conan, even with sufficient permissions. |
Fixed an issue whereby, SAML SSO users saw an incomplete Set Me Up page in some repositories. | |
Fixed an issue whereby, anonymous users were not getting the configuration settings from the Set Me Up instructions for the corresponding repositories. | |
RTDEV-33659 | Fixed an issue whereby, Artifactory served the entire versions file (Gems compact index) instead of the delta. |
RTDEV-30603 | Fixed an issue whereby, Artifactory returned |
Fixed an issue whereby, SHA-256 checksum was not implemented in the Puppet repository metadata. | |
RTDEV-33083 | Fixed an issue whereby, the |
Fixed an issue whereby, Artifactory did not cache all the Yum remote repository metadata when the | |
Fixed an issue whereby, creation of new indexes failed during Artifactory upgrade when Microsoft SQL Server (MSSQL) was running with a non-enterprise edition. | |
Fixed an issue whereby, Artifactory returned an error while publising an npm package with a size exceeding 5MB. |