-
Notifications
You must be signed in to change notification settings - Fork 116
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
accesing /pulp/api/v3/ requires auth since 3.16, while didn't before #2340
Labels
Comments
lubosmj
added a commit
to lubosmj/pulpcore
that referenced
this issue
Jun 1, 2022
lubosmj
added a commit
to lubosmj/pulpcore
that referenced
this issue
Jun 1, 2022
lubosmj
added a commit
to lubosmj/pulpcore
that referenced
this issue
Jun 10, 2022
lubosmj
added a commit
to lubosmj/pulpcore
that referenced
this issue
Jun 15, 2022
lubosmj
added a commit
to lubosmj/pulpcore
that referenced
this issue
Jun 15, 2022
lubosmj
added a commit
to lubosmj/pulpcore
that referenced
this issue
Jun 16, 2022
lubosmj
added a commit
to lubosmj/pulpcore
that referenced
this issue
Jun 16, 2022
lubosmj
added a commit
to lubosmj/pulpcore
that referenced
this issue
Jun 16, 2022
lubosmj
added a commit
to lubosmj/pulpcore
that referenced
this issue
Jun 17, 2022
ipanova
pushed a commit
that referenced
this issue
Jun 20, 2022
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Version
3.16.3
Describe the bug
since 3.16 accessing
/pulp/api/v3/
requires auth, while before that it did not.I think this is a side effect of #1593, just not sure if that was intentional or not.
To Reproduce
Steps to reproduce the behavior:
curl -k https://localhost/pulp/api/v3/
Expected behavior
Until 3.15, this would return 200, now it returns 403, unless I do provide auth.
Accessing
/pulp/api/v3/status/
still works fine without auth.Additional context
Originally found while working on Puppet integration of 3.16+ in theforeman/puppet-pulpcore#249
The text was updated successfully, but these errors were encountered: