Azure / acr

Azure Container Registry samples, troubleshooting tips and references
https://aka.ms/acr
Other
162 stars 106 forks source link

Cannot list registry with metadata/read and content/read permissions #675

Closed hayk99 closed 1 year ago

hayk99 commented 1 year ago

Describe the bug I am doing a couple of tests with Azure Registry Container. My goal is to be able to list the whole registry with a token that has a scope map with the following setup.

After creating this token I tried to list all the registry by triggering a get to the/_catalog and got this error

GET https://testregistryscanner.azurecr.io/v2/_catalog?n=1000: UNAUTHORIZED: authentication required, visit https://aka.ms/acr/authorization for more information.; [map[Action:* Name:catalog Type:registry]]

This workflow does not throw the above error if I use _repositories_admin (azure manged) scope map.

To Reproduce

Steps to reproduce the behavior:

  1. Create a scope map and assign it to a token with the following setup repo-by-repo

A small note regarding the scope map creation: it will be great to have wildcards like "*" so the user can specify the permission to the whole registry instead of going one repository by one (imaging large registries).

  1. Use the token to authenticate against the API

Expected behavior It would be great to be able to list the whole registry with metada/readand content/read permissions.

Screenshots If applicable, add screenshots to help explain your problem.

Any relevant environment information

Additional context Trying to fetch repositories using the docker v2 API

If any information is a concern to post here, you can create a support ticket or send an email to acrsup@microsoft.com.

terencet-dev commented 1 year ago

Hi @hayk99,

Please open a support ticket with our team to investigate as this board is primarily used to provide roadmap updates. If you don’t have any additional questions here, this issue will close in 7 days. Thanks!

hayk99 commented 1 year ago

Thank you!

terencet-dev commented 1 year ago

Closing as this issue is now inactive for over 7 days. Thanks!