In some cases, Following the appearance of “Exception message:
It is recommended to upgrade to Artifactory version 7.59 or higher.
Build info links containing artifactory/webapp in the URL are redirected to the packages page in the JFrog Platform UI:
instead of the information page for the selected build number.
Workaround:Edit the URL manually by removing the packages# prefix. This fix will redirect the link to the build number information page:
OpenJdk17.0.3, which is bundled with Artifactory 7.46/7.47/7.49 has a bug in the newrelic java agent, which causes Artifactory to fail to start up.
When modifying the userLockPolicy settings through the YAML configuration file, the changes were not applied accordingly.
Customers with an Enterprise+ subscription that have Access Federation enabled will lose the Access Federation setup as a result of editing the security configurations UI.
The default expiration of Access Tokens created by the deprecated Artifactory Create Token REST API (
NPM installation fails if a bundledDependencies is present in the package.json.
The List Docker Tags API does not work as expected - when executing this API, Artifactory queries the remote resource only once and caches the response. As a result, it will always use the cached response and will not query the remote again.
Users are unable to log into Artifactory when there is an IP address in the X-Forwarded-For Header in the format <ip:port> in the schema name.
Add a header rewrite for X-Forwarded-For header in the application gateway. The header value should be:
Users performing Google authentication to the JFrog Platform will receive an error.
When there are more than five outbound servers configured in Access Federation, Artifactory fails to start.