Closed vigneshrajap closed 1 year ago
Can you tell whether this is true for all pulp endpoints? From the looks of it, it may not even be an issue with the cli...
@mdellweg pulp status
and pulp orphan cleanup
still work with Remote user authentication but anything with pulp deb **
does not work.
Based on the http
output, pulp-cli isn't the problem here, it's something on the server-side.
@vigneshrajap status and orphan-cleanup aren't list-endpoints, so I don't think they're helping us pin this down. On your system, what does http --cert $cert --cert-key $cert_key $BASE_ADDR/pulp/api/v3/artifacts/
return? If it's a "typical" list-response (count/next/prev/results), then it "feels like" the pulp_deb repo-list REST API is the more-likely culprit.
@ggainey Yes I agree, the issue seems to be on the server side. but I am not sure where I should ask about it.
http --cert $cert --cert-key $cert_key $BASE_ADDR/pulp/api/v3/artifacts/
could not be accessed and it outputs as "detail": "Authentication credentials were not provided."
Some configuration for remote user authentication has been set incorrectly I believe. Thanks for the help, i will close the issue.
@vigneshrajap you can always hit us up in #pulp in Matrix, or open a thread in discourse:
There seems to be a slight difference between extracting information using Basic authentication and using Remote User authentication. I have attached both examples.
http --auth username:password $BASE_ADDR/pulp/api/v3/repositories/deb/apt/
http --cert $cert --cert-key $cert_key $BASE_ADDR/pulp/api/v3/repositories/deb/apt/
Due to this difference, pulp cli deb is throwing error since it tries to access data through "results"
pulp deb repository list