The following table lists the set of known issues in Artifactory including the version in which they were discovered, and the version in which they were fixed. Click the issue ID for full details in JIRA.
| Issue ID | Description | Affected From Version | Fix Version |
|---|---|---|---|
| RTFACT-20296 | When running with Microsoft SQL database, after upgrading to version 6.13, deploying/deleting artifacts/directories and deleting existing repositories will fail with an error. | 6.13.0 | 6.13.1 |
| Private JIRA | Working with Azure blob storage as the Artifactory binary provider, in some cases would result in timeout errors for uploads/downloads | 6.10.1 | 6.10.2 |
Users associated with a group that is configured with admin privileges and additional non-admin group(s), do not have admin privileges. | 6.8.0 | 6.8.4 | |
| After upgrading to Artifactory 6.8.0 or above, signing or distributing a Release Bundle from Distribution will fail | 6.8.0 | 6.8.2 | |
| RTFACT-18524 | Upgrade will fail if loginBlockDelay is set to 0 | 6.7.0 | 6.8.1 |
| RTFACT-18745 | After upgrading Artifactory to 6.6 and above, starting Artifactory can take long period due to index validation in the Oracle database | 6.6.0 | 6.8.7 |
| RTFACT-18502 | Massive permission target can consume excessive amount of memory | 6.6.0 | 6.8.1 |
| RTFACT-16246 | Import of security configuration file with large number of groups/permissions/users can fail | 5.8.3 | 6.5.3 |
JFrog Artifactory 6.3.0 is not backwards compatible with previous versions for the purposes of distributing release bundles. Therefore, when distributing release bundles between Artifactory services with JFrog Distribution, you need to ensure that either both source and target services are version 6.3.0 and above, or they are both below version 6.3.0. | 6.3.0 | 6.3.0 | |
| RTFACT-17418 | With DB sessions, Artifactory leaves an open transaction after forwarding a servlet request. | 6.2.0 | 6.3.2 |
| RTFACT-17228 | Mission Control DR security replication functionality is broken for Artifactory due to some security changes in Artifactory and Access (security component) | 6.1.0 | 6.3.0 |
| RTFACT-17060 | Upgrading to Artifactory 6 will fail if SSL / TLS certificate is configured on one or more of the remote repositories | 6.0.0 | 6.2.0 |
| RTFACT-16905 | When working with npm repositories, authenticating against Artifactory using the Registry returned 401 for PUT on <Artifactory URL>/api/npm/<repo name> | 6.0.2 5.11.1 | 6.1.0 5.11.2 |
| When working with the S3 cloud binary provider and the "Storage Quota Control" feature is enabled, in edge cases of multiple concurrent deployments, artifacts deployment may fail. | 5.9.0 | 5.11.0 | |
| When working with Helm remote repository that proxies https://storage.googleapis.com/kubernetes-charts, Artifactory fails to index. Resolving packages from the repository fails. | 5.8.0 | 5.9.0 | |
| RTFACT-15679 | When performing a System Import on an Artifactory instance running version 5.7 and above, and the folder being imported was exported from Artifactory 5.7.x or 5.8.x, when the import process is completed, Permissions will have not been imported and are missing from Artifactory. To work around this known issue, and retrieve the Permissions, take the following steps:
| 5.7.0 | 5.9.0 |
| RTFACT-15580 | When upgrading from version below 5.7 to version 5.7 and above while the Artifactory password encryption is enabled, Artifactory will fail to start up with the following error in logs: | 5.7.0 | 5.8.1 |
| RTFACT-15315 | Running | 5.6.0 | 5.6.1 |
| RTFACT-15297 | For Artifactory HA installations, single-phase upgrades (with downtime) from version 4.x to version 5.6 without going through version 5.4.6 fails. Please refer to the Upgrade Notice in the Artifactory 5.5 Release Notes. | 5.6.0 | 5.6.1 |
| RTFACT-14672 | Git LFS client v1.x working against Artifactory Git LFS repository using SSH fails to upload or download LFS blobs. | 5.3.0 | 5.4.6 |
| RTFACT-14473 | When resolving a package from an npm repository, Artifactory throws a deserialize error to the log file if one of the package's dependencies in the corresponding “<dependency_name>” : { “version” : “<version_number>” }. For example: "deep-diff" uses this format. As a result, the npm client fails to resolve the package. Note: For a workaround, please refer to the issue details. | 5.4.0 | 5.4.6 |
| RTFACT-14687 | A system import on a High Availability installation of Artifactory 5.4.x with files exported from a version that is below 5.4, will fail. | 5.4.0 | 5.6.0 |
| RTFACT-14530 | After upgrading an Artifactory HA cluster from version 5.x to 5.4.x, new nodes that you add to your Artifactory HA cluster will not start up. | 5.4.0 | 5.4.4 |
| Uploading or downloading files to Artifactory using access tokens with a subject that is longer than 64 characters fails with error 500. | 5.4.2 | 5.4.3 | |
| RTFACT-14477 | Artifactory fails to start up when Tomcat is configured to only use HTTPS, or was configured with both HTTP and HTTPS but on different ports. | 5.4.0 | 5.4.2 |
| RTFACT-14495 | Artifactory is unable to connect to access service and as a result cannot start when Tomcat is configured with a Self-Signed chain certificate. | 5.4.0 | 5.4.2 |
Following an upgrade from Artifactory version 4.4 or below to 5.3 directly, Artifactory will fail to start up. Note: Upgrading from version 4.4.1 and above to 5.3 is not affected and Artifactory will start up after the upgrade. | 5.3.0 | 5.3.1 | |
| RTFACT-13870 | Deploying artifacts larger than 100MB in size when using an S3 compatible storage provider can fail leading to unpredictable results. | 5.1.2 | 5.1.3 |
User Plugins that contain the realms execution point will fail to be executed and throw an | 5.0.0 | 5.11.1, 6.0.1 | |
| RTFACT-13923 | Artifactory might not start up following an upgrade to version 5.x on Windows when Artifactory is configured with a Keystore. | 5.0.0 | 5.1.4 |
| RTFACT-13822 | Most downloaded widget in Artifactory home can cause the DB to stall. | 5.0.0 | 5.1.3 |
| RTFACT-14079 | When using FullDB or S3 as a binary provider and an NPM virtual repository, external dependencies cause a leak of resources that exhausts all of the DB connections that are never freed. | 4.16.0 | 5.3.0 |
| "downloadTagFile" and "downloadBranchFile" API endpoints throw a nullPointerException when a VCS remote repository has "Store Artifacts locally" disabled | 4.16.0 | ||
| RTFACT-8503 | When viewing Smart Remote Repositories in the tree browser, folders under the repository that contain a space in their names, will not expand. | 4.0.0 | |
| RTFACT-8194 | 'docker pull' fails on remote repositories when 'Store Artifacts Locally' is disabled. | 3.9.0 | |
| RTFACT-11942 | '
| 3.4.2 | |
| RTFACT-13004 | When trying to retrieve an item's properties from Docker V2 repositories using the /api/storage REST API endpoint, a 401 error is returned to the client. | 3.4.2 | |
| RTFACT-12710 | Python metadata calculation will fail if the Python metadata version is set to 1.2 inside the METADATA or PKG-INFO files. | 3.4.0 | 5.4.0 |
| RTFACT-12379 | NuGet virtual repositories that aggregate more than one local or remote repository may omit results when searching for a package | 2.5.0 | 5.2.1 |
| RTFACT-10132 | 'NuGet install' does not enforce include / exclude patterns on virtual NuGet repositories | 2.5.0 | 5.7.0 |
| RTFACT-12959 | Anonymous users cannot download folders even if anonymous access is enabled. | 2.0.0 | 5.6.0 |
| RTFACT-6485 | Uploading a file containing a dot in the target path will fail and a 500 error will be returned to the client Note: The | 2.0.0 | 5.4.0 |
When all artifacts have been deleted from a folder, the folder is not pushed to the pruning queue even though it is empty, and is, therefore, not deleted. | 2.0.0 | ||
| RTFACT-12260 | When performing a full system export on an instance with blacked out repositories, and then doing a corresponding import on a target instance, the content and metadata of the blacked out repositories are not imported. | 2.0.0 | |
| RTFACT-9343 | Promoting Build Info that contains a dependency or an artifact that has the same checksum of an item that already exists may result in a race condition for the same target path. | 2.0.0 |