After enabling client certificate authentication: Error: {"detail":"Authentication credentials were not provided."}
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 35/100
- Issue type
- Bug
- Clarity
- Mostly clear
- Activity status
- Stale
- Tech stack
- python
- Domain
- authentication, cli, security
Research direction
Start by reproducing the verbose pulp --config secret/cli.toml --verbose rpm repository list request with PULP_CA_BUNDLE set, then inspect how pulp-cli combines client certificates, CA bundles, and admin credentials. The secret/cli.toml configuration and PULP_CA_BUNDLE environment variable are the concrete inputs. Done means the authenticated request returns the repository list when client certificate authentication is required.
Written by the indexing model from the issue text.
Description
Summary
[cli]
base_url = "https://pulp3.hostname.tld"
username = "admin"
password = "password"
api_root = "/pulp/"
domain = "default"
format = "json"
cert = "secret/client.cert.pem"
key = "secret/client.key.pem"
verify_ssl = true
First I got CERTIFICATE_VERIFY_FAILED because pulp cli config file has no option for providing CA certificate bundle.
After enabling environment variable export PULP_CA_BUNDLE="secret/ca.crt" a new error appears:
$ pulp --config secret/cli.toml --verbose rpm repository list
repositories_rpm_rpm_list : get https://pulp3.hostname.tld/pulp/api/v3/repositories/rpm/rpm/?offset=0&limit=25
Response: 401
Error: {"detail":"Authentication credentials were not provided."}
Admin credentials didn't change, i just added client certificate authentication requirement to relevant ingress.
Steps to reproduce
As provided above
Expected behavior
pulp cli would return repository list
Pulp and pulp-cli version info
pulp-cli version:
$ pulp --config secret/cli.toml --version
Pulp3 Command Line Interface, Version 0.29.1
Plugin Versions:
common: 0.29.1
Pulp version:
latest default images from pulp-operator
- Dominant language
- Python
- Stars
- 43
- Forks
- 52
- Avg merge
- 11h 38m
- Merged PRs (30d)
- 11
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from pulp/pulp-cli
-
bug Triage-Needed
Difficulty 2/5 1-3 hours Newbie friendliness 58/100
-
Difficulty 3/5 1-2 days Newbie friendliness 45/100
-
feature request
Difficulty 4/5 3-5 days Newbie friendliness 35/100
-
easy fix feature request
Difficulty 3/5 1-2 days Newbie friendliness 25/100
-
bug Triage-Needed
Difficulty 4/5 3-5 days Newbie friendliness 42/100
Similar issues
-
essnmx good first issue
Difficulty 1/5 Under an hour Newbie friendliness 95/100
-
[Feature] 奇物选择添加优先级 Open
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
syfoud/Simulated_Scepter#174 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
Giskard-AI/giskard-oss#2840 · 1 comment ·
-
A claim comment carrying the issue number is silently declined while the workflow reports success Openarea: repo bug perceived difficulty: 2
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
yeti-platform/yeti#1380 ·