Repository navigation
pulp-cli 0.41 break username password auth in older configs (cert and key present but empty) #1487
Description
Summary
Starting in v0.41 of pulp-cli, empty cert and key break username password authentication
Steps to reproduce
- ensure in
~/.config/pulp/cli.toml, for instance by generating with pulp-cli version 0.37.2
[cli]
(...)
username = "admin"
password = "xxx"
verify_ssl = true
cert = ""
key = ""
-
install pulp-cli 0.39
-
verify
pulp user liststill works -
update pulp-cli from 0.39 to 0.41
Expected behavior
pulp user list still works
Stacktrace/Error log
Www-Authenticate: Basic realm="api"
X-Content-Type-Options: nosniff
X-Frame-Options: DENY
b'{"detail":"Authentication credentials were not provided."}'
Error: Authentication failed for users_list.
Pulp and pulp-cli version info
Pulp3 Command Line Interface, Version 0.41.0
Plugin Versions:
common: 0.41.0
Additional context
A config created by pulp-cli 0.37.2 has the empty string values for cert and key
Activity
mdellweg commentedon Oct 13, 2026
How did the old installation authenticate when nothing is specified?
elelaysh commentedon Oct 13, 2026
I had username/password in the config
(adding to repro steps)
mdellweg commentedon Oct 14, 2026
Can you attach the output of
pulp debug openapi security-schemesand
pulp debug openapi spec | jq '.paths."{auth_user_href}".get.security'mdellweg commentedon Oct 14, 2026
The only change i see that this would affect is that the cli would try to use the cert (specified wrongly as the empty string) (and fail) even in 0.39 if not username had been provided, but with 0.41 it actually prefers using that mechanism over basic auth.
I think you should remove the keys from the config.
elelaysh commentedon Oct 15, 2026
Thank you: I've already removed the empty strings.
Please can you add something to the release notes? Because I think every user with a 0.37-generated config will have the issue.
Validate credentials in config to be non-empty
Validate credentials in config to be non-empty
mdellweg commentedon Oct 15, 2026
Thank you for reporting this. The cli now fails on startup (validating the config) so a user just has to take action. Silently failing and hiding the root cause really was not nice.
elelaysh commentedon Oct 15, 2026
Thank you for the fix :-)
Validate credentials in config to be non-empty
Validate credentials in config to be non-empty