-
Notifications
You must be signed in to change notification settings - Fork 45
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Discrepancy beetween what a user can pull and see in catalog with token_auth off #1651
Labels
Comments
ipanova
changed the title
Disrepancy beetween what a user can pull and see in catalog with token_auth off
Discrepancy beetween what a user can pull and see in catalog with token_auth off
May 29, 2024
We need to add a test when token auth is disabled, non-authed user should be able to see public and private repos in the catalog |
git-hyagi
added a commit
to git-hyagi/pulp_container
that referenced
this issue
Jun 18, 2024
With token-auth disabled, allow non-authed users to see all repos (public and private) in catalog. closes: pulp#1651
git-hyagi
added a commit
to git-hyagi/pulp_container
that referenced
this issue
Jun 19, 2024
With token-auth disabled, allow non-authed users to see all repos (public and private) in catalog. closes: pulp#1651
github-project-automation
bot
moved this from In Progress
to Done
in Pulp Container Roadmap
Jun 20, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Version
Please provide the versions of the pulpcore and pulp_container packages in use, and how they are installed. If you are using Pulp via Katello, please provide the Katello version.
Describe the bug
A clear and concise description of what the bug is.
To Reproduce
Disabled token_auth
Create a mix of public and privates repos. Notice that non-authed user can pull privately marked repo but does not see it in catalog.
Expected behavior
With token-auth disabled, non-authed user should see all repos in catalog (private and public) and pull also all of them
Additional context
#1649 (comment)
The text was updated successfully, but these errors were encountered: