|Issue ID||JFrog Product||Description||Affected From Version||Fix Version||Additional Information|
|Pipelines||The runtrigger crashes, which causes the pipeline to get triggered multiple times.||1.18.0||1.18.1|
|Pipelines||The "Uploading step information' was looped 270 times for a single step that errored out.||1.18.0||1.18.1|
|Pipelines||The Jenkins Native steps get stuck.||1.18.0|
|Distribution||Conflicting target path for the Docker layers||2.9.0||2.9.1|
|Xray||The scan build times out when the build name contains '/'||3.27.0||3.30.2|
|RTFACT-26250||Artifactory||The link to the HTTP-SSO does not work after the upgrade and generates an error message.||7.24.3||7.24.6|
|Artifactory||Artifactory fails to start due to a circular reference of ||7.26.0||7.26.1|
|Artifactory||MDS migration causes the distributed_locks table to bloat during a 6.x to 7.x upgrade.||7.2.1||7.24.0|
|Artifactory||Using join key twice (in file and system.yaml) causes startup failures||7.2.1||7.11.1|
|Artifactory||The Conan repositories created in the Free Trial are broken in version 7.9.0: Free Trial instances do not support Conan repositories; therefore, it is not possible to configure users using Conan repositories. ||7.9.0||7.10.5|
|Artifactory||System messages do not work in the UI.||7.8.2||7.9.0|
|RTFACT-23368||Artifactory||When an Azure guest user tries to log in to Artifactory, they are not able to log in successfully.||7.7.3||7.10.1|
|Artifactory||Artifactory 7.8.0 does not start up after upgrading from Artifactory 6.21.0.||7.8.0||7.8.1|
|Artifactory||Unable to run Singleton type tasks, such as garbage collection. Singleton type tasks are marked with markers to decide if they can run and stop other tasks from running.||7.6.2||7.7.0|
Because the addition of the "Allow Content browsing" in feature allowed stored XSS and phishing, an addition was made to version 6.23.16 to remove this potential security issue. However, this addition can lead to problems with accessing resources like XML, HTML due to the new CSP header "Content-Security-Policy: sandbox".
|RTFACT-22591||Artifactory||When trying to pull Docker images through ||6.20.0||7.6.4, 6.21.0|
|Artifactory||PostgreSQL driver should not be bundled in WARs but under tomcat/lib (the Postgres driver is being added twice in Docker containers: both as part of the Artifactory war (||7.6.1||7.7.0|
|Artifactory||Artifactory failed to start after redeployment.||7.5.2||7.6.1|
|Artifactory||Artifactory fails to start in Azure SAAS due to "||7.6.0||7.6.1|
|Artifactory||Setting the default system proxy also changes the existing remote repositories definition.||7.0.0||7.27.0|
|RTFACT-21838||Artifactory||Nuget local repository may return an incorrect version when ||6.19.0||7.5.0, 6.20.0, 6.19.1|
Re-indexing a path on the metadata server will cause a connection leak and eventually a starvation of connections of the database connection pool, due to a query with a lazy AQL query with an unclosed result set.
Artifact search performance issue due to case-insensitivity.
From Artifactory 7.0.0, the "artifact search" via UI/API is case-insensitive by default. The case-insensitive search can be disabled by applying the following property:
Database Schema Known Issues
The JFrog Platform requires a common database upgrade infrastructure for all products. Currently, each product has a different implementation, so the following database schema-related issues are also addressed in this Known Issues document.
|Issue ID||Description||Affected From Version||Fix Version||Additional Information|
|Problems when upgrading from 6.16.2 to 7.7.8||7.7.8|
|Artifactory does not cleanly remove deleted configuration import files||7.12.6||7.23.3|
|The security.<timetstamp>.xml file is being synced between nodes after upgrade upon Artifactory start process||7.5.7||7.23.3|