Issue ID | Description | Fix Version | Additional Information |
|---|---|---|---|
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. | 7.49.6 | ||
JA-4703 | Any changes made to the security configurations Web will override the custom configurations defined in the Access YAML Configuration. | 7.47.15 | Customers with an Enterprise+ subscription that have Access Federation enabled will lose the Access Federation setup as a result of editing the security configurations WebUI. |
Any external user (SAML, LDAP, OAuth, etc.) and users who previously had admin privileges are no longer able to be added via the UI to any Permission Target. | 7.47.12 | Workaround: You can add the user to the permission target with the Create or Replace Permission Target REST API. | |
When trying to initialize a new remote CocoaPods repository with GitHub, if the default branch on GitHub is not ‘master’, Artifactory will return a 404 error. | 7.55.1 | Workaround: Create a branch with the name ‘master’ and make it default. The initialize should work after that. | |
JA-4324 | Enabling anonymous access can cause Artifactory operate in unhealthy mode, meaning that the WebUI continuously displays the message "JFrog Platform will be available shortly". | 7.47.12 |