Issue ID | JFrog Product | Description | Fix Version | Additional Information |
|---|---|---|---|---|
JA-4390 | Platform | gRPC requests fails when user has a lot of groups. | 7.49.5 | |
JA-4174 | Platform | The Reset MFA Enrollment button is always disabled in the User edit page. | 7.49.5 | |
JFUI-11513 | Platform | The "Create New Application Integration" page is missing from Artifactory. | ||
JA-3433 | Platform | A 500 error is received when trying to edit a Permission Target updated via REST API. | 7.46.3 | |
Artifactory | Edge Node smart repository behavior: Able to successfully download the artifacts that exist under the smart remote cache repository of the Edge Node instance when the connection to the source Artifactory instance is lost. | 7.46.3 | ||
RTDEV-28161 | Artifactory / Distribution | In some cases, during a simultaneous distribution of Release Bundle versions that have artifacts with similar parent paths (BulkCopyOnMove mechanism), the distribution may fail silently (i.e., the Release Bundle version distribution will be marked as completed successfully despite the fact that the artifacts are not displayed in the target). | 7.47 | |
Artifactory / Distribution | AQL queries are able to consume massive amounts of database CPU after some time. | 7.46.3 | Distribution relies on AQL to find artifacts for a release bundle; however, if the customer has a lot properties, this becomes heavily inefficient, as some some AQL queries will take over an hour to complete, and hamper database performance. | |
PIPE-8688 | Pipelines | Installing with a custom CA causes connections to public providers to fail. | 1.25.0 | |
PIPE-9075 | Pipelines | Pipelines does not work with the default Helm Chart settings. | Websockets do not work with Artifactory's nginx configuration. You may want to use ingresses when using Pipelines as a workaround. | |
JR-5590 | Distribution | Signing a release bundle that includes artifacts from the build with the name or with a number larger than 64 chars fails. | 2.13.4 | |
XRAY-8838 | Xray | When invoking the build-scan API (via the JFrog CLI) the URL that is returned leads to a 404 when the scan occurs on a build that is in a non-default project. | 3.37.2 | |
RTDEV-26980 | Artifactory | When uploading a file that already exists in the object store remains in eventual. | ||
JR-5440 | Distribution | Signing release bundles with a passphrase works only with the default GPG. | ||
RTDEV-26800 | Artifactory | When setting multiple replications per repository in the UI, there is no way to set a dedicated cron expression for each replication. Only a single one in the main screen. | Suggested Workaround: Use the Multi-push Replication API and set the cron per entry. | |
Artifactory | VCS Remote to Azure-hosted Repositories is not supported in Artifactory. | Currently Azure-hosted repositories are not supported. | ||
Artifactory | The | The repository ID of the actual repository from which the artifact was requested in the callback is unknown in the case of virtual repositories. | ||
A thread leak in the access-go-client causes an error. From Artifactory 7.38.7 also affects Xray. | 3.50.0 | Fixed in Xray version. | ||
Many grpc calls are being blocked because of a platform performance issue: in these cases there are many threads waiting for a cache to be initialized in permissions. | 7.38.7 | Suggested Workaround: If you are not using Projects, you can change the parameter
| ||
RTFACT-25553 | Artifactory / Distribution | Edge Webhook - Artifactory Release Bundle Domain should be Release Bundle. The Artifactory Release Bundle domain has been renamed Destination to consolidate all under same Release Bundle domain. | Artifactory 7.18.0 Distribution 2.10.5 | |
Distribution | Slowness issue in the release bundles list page. | Distribution 2.10.3 | ||
Distribution | In cases where the Mission Control token had an extended expiration, the connection of the Distribution instance to the remote Mission Control using a circle of trust for token validation fails. | Distribution 2.9.3 | ||
Xray | Artifacts are not indexed and the persist queue continues to grow when the number of persisted workers is increased without properly updating the max-connections configuration. | The issue has not been resolved but a watchdog was introduced to enable faster detection of the misconfiguration. When the problem occurs, the following warning willl appear in the log file: "All db connections are in use (30/30) for 3m. service might not be functioning. Consider increasing the persist.database.maxOpenConnections configuration parameter". |