ruby bindings seem to always set Authorization header
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 598
- Forks
- 168
- Avg merge
- 1d 4h
- Merged PRs (30d)
- 86
Description
Author: @dkliban (dkliban@redhat.com)
Redmine Issue: 6246, https://pulp.plan.io/issues/6246
It seems that even when the client is configured with aclient cert and key, the client bindings are setting Authorization header. If the BasicAuthorization is enabled on the server, the user is not able to authenticate using the client cert and key. Removing the BasicAuthorization resolves the problem.
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.
Research direction
Start by locating the Ruby client bindings' authentication and request-header handling, then reproduce the case with a client certificate and key while BasicAuthorization is enabled on the server. Done means certificate authentication works without the bindings sending an Authorization header in that configuration; add or run focused coverage for this behavior if the project provides it.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python, ruby
- Domain
- authentication, security
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100