Artifactory 7.84

Issue ID	Description	Fix Version	Additional Information
RTFACT-31038	An unannounced change was introduced by Conda Forge upstream which impacts Artifactory's ability to resolve package metadata and dependencies with virtual Conda repositories. For more information see this article.	7.84.23	Suggested workaround: Use the Conda Remote Repository Directly: Instead of relying on the Virtual Conda repository, users can directly use the Conda remote repository (repo.anaconda.com/conda-forge) to download packages.
RTDEV-46858	Redirect Signed URLs will not work when using the cluster-sharding provider with a cloud provider in the binarystore chain and templates such as: cluster-s3-storage-v3, cluster-google-storage-v2 and cluster-azure-blob-storage-v2.	7.90.9	Suggested workaround: To mitigate this issue, switch to use a direct chain such as: s3-storage-v3-direct.
RTDEV-44298	The `artifactory.aql.queries.limit.enabled` feature flag was set to `true` in Self-Hosted environments, causing users to receive a "too many requests" response with the status code 429. There is a feature in Artifactory that limits the number of search/AQL requests that can run in parallel. The relevant flags include: `artifactory.aql.queries.limit.enabled`: This is the boolean flag for enabling the feature. It is currently set to `true` by default, which can cause the 429 response described above. In upcoming versions, this flag will be set to `false` by default. `artifactory.aql.queries.unlimited.agents`: The list of user agents that are not limited by the API. The default values are `pipeline, artifactory, xray, distribution`. `artifactory.aql.queries.limit`: The limit on API calls that can run in parallel. If the limit is reached and the number of calls does not drop below the limit before the timeout occurs (see the next flag), a "too many requests" response is sent with the status code 429. The default is `3`. `artifactory.aql.queries.pending.timeout.millis`: When the query limit is reached, this is the amount of time a current call is locked while it tries to acquire the AQL search. If the number of calls is still at the limit when the timeout is reached, a "too many requests" response is sent with the status code 429. The default is `10000` ms.	7.84.16	Suggested workaround: Add the line: `artifactory.aql.queries.limit.enabled=false` to the $JFROG_HOME/artifactory/var/etc/artifactory/artifactory.system.properties file.
RTFACT-30345	In multisite environments where Mission Control is in use, any JPD with a configured Federated Base URL (federatedRepoUrlBase) will not appear as an option in the Deployments tab. This prevents you from adding a Federated repository in that JPD as a member of the Federation. Note This known issue is a general limitation that applies to all versions.	TBD	As a workaround, you can add members by entering the full address in the URL tab.

Note