Released: 7 July, 2023
API Key Deprecation
As notified in Artifactory 7.47.10, support for API Key is slated to be removed in a future release. To ease customer migration to reference tokens, which replaces API key, we are disabling the ability to create new API keys at the end of Q3 2024. The ability to use API keys will be removed at the end of Q4 2024. For more information, see JFrog API Key Deprecation Process.
Known Issue in this Version
under some circumstances, users who attempt to modify their binary-store.xml configuration file might experience files being deleted. Users with Sharding Cluster and Eventual Cluster configured should upgrade to version 7.63.11 or higher. For more information, see Known Issues.
Resolved Issues
JIRA Issue | Description |
|---|---|
Fixed an issue whereby, Artifactory did not support deleting remote repositories with a name ending in | |
Fixed an issue whereby, when performing a search in a Conan repository with insufficient permissions, future Conan searches did not work as expected, even with sufficient permissions. | |
Fixed an issue whereby, when logging in to the JFrog Platform using SAML SSO with the permissions to Edit Profile, the Configure screen of the Set Me Up was missing from the WebUI. | |
Fixed an issue whereby, when logging in as an anonymous user, the Configure screen of the Set Me Up was missing from the WebUI. | |
Fixed an issue related to npm whereby, when publishing a package with a size exceeding 5 MB, Artifactory returned an error. | |
RTDEV-33502 | Fixed an issue whereby, when getting the Crowd settings using the Artifactory WebUI, the settings were not fetched correctly. |