pulp / pulp/pulpcore

As a user, I can configure my remote to use basic auth and proxy without a password

Open
#2,081 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Feature Katello satellite
Dominant language
Python
Stars
598
Forks
168
Avg merge
1d 4h
Merged PRs (30d)
86

Description

Author: @goosemania (ttereshc)

Bugzilla: https://bugzilla.redhat.com/buglist.cgi?quicksearch=1951673
Redmine Issue: 8602, https://pulp.plan.io/issues/8602


Some providers like packagecloud.io, ask to use basic auth with no password https://packagecloud.io/docs/api.
Without allowing it, our users won't be able to sync from certain providers.

RFC 2617 seems to allow empty passwords https://tools.ietf.org/html/rfc2617#section-2

password = *TEXT

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

No source file or test is named. Start by reading the packagecloud API documentation and RFC 2617 section 2, then trace where remote basic-auth and proxy credentials are validated. Done means a remote can use basic authentication with an empty password, including when a proxy is configured, without breaking existing credential handling.

Written by the indexing model from the issue text.

Assessment

Tech stack
python
Domain
authentication, backend
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
45/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.