[bug] Workflow with Artifactory Virtual Repository breaks with Read-only user

[rconde01]

Describe the bug

I have a virtual repository on Artifactory CE which maps to a local repository and to conan center. I wanted to have some users which were read-only. However, for these users - it often breaks saying it can't find a conan center recipe in the remote. In Artifactory the logs look like:

2024-05-26T18:00:29.465Z [jfrt ] [ERROR] [5cd4193084565ace] [r.v.ArtifactoryRepoService:207] [ttp-nio-8081-exec-31] - Couldn't read index file in remote repository _my_conan_center : User read_only_user is not permitted to deploy '_/glslang/11.7.0/_/index.json' into '_my_conan_center-cache:_/glslang/11.7.0/_/index.json'.

Basically, it looks like it prevents read-only users from updating the cache - which doesn't really make sense.

How to reproduce it

No response

[memsharded]

Hi @rconde01

have a virtual repository on Artifactory CE which maps to a local repository and to conan center.

Please note that this is not necessarily the setup that we recommend for using ConanCenter packages in production. Please check https://docs.conan.io/2/devops/using_conancenter.html, and see how the remote repo is not the approach there, but using your own local repo, and uploading there your binaries that you create. The issues would be:

• Changes in ConanCenter are propagated to remotes, so potential instability caused by new package versions, changes in existing packages, etc, can impact your builds as if you depended directly on ConanCenter
• Outages in ConanCenter will still disrupt your builds, until some admin goes and manually marks the repo as offline

Otherwise, I think that looks like an issue in Artifactory, I'd recommend to file a ticket in their system directly, then you can share with me and I can try to track it, but it is generally better if Artifactory users report these issues directly.