|Issue ID||Description||Affected From Version||Fix Version|
|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.
|RTFACT-14063||An external user who has created a token will still be able to refresh it even if he has been removed from the external authentication server.||5.2.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|
JFrog Mission Control reload plugin may get into a loop.
Note that as a workaround this plugin can be removed since it is no longer used if working with Artifactory version 5.0.0 or above.
|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|
Most downloaded widget in Artifactory home can cause the DB to stall.
|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|
When viewing Smart Remote Repositories in the tree browser, folders under the repository that contain a space in their names, will not expand.
|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|
Python metadata calculation will fail if the Python metadata version is set to 1.2 inside the METADATA or PKG-INFO files.
NuGet virtual repositories that aggregate more than one local or remote repository may omit results when searching for a package
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.
|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-12934||A Maven virtual repository does not return the correct latest snapshot if another package with the same version number exists in a different repository.||2.0.0|
|RTFACT-12959||Anonymous users cannot download folders even if anonymous access is enabled.||2.0.0|
Uploading a file containing a dot in the target path will fail and a 500 error will be returned to the client
|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|