Allow authentication methods to set client certficates
Open
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 54.3k
- Forks
- 10.4k
- Avg merge
- 16h 43m
- Merged PRs (30d)
- 3
Description
Currently authentication methods can configure all the request options except for the cert option (the verify option also cannot be specified, but I don't a need for that). Would a PR to allow the setting of cert on the request object to be propagated up to send be acceptable?
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
Trace how authentication methods configure request options and how those options reach send. Confirm where the cert option is currently omitted, then verify that setting it on the request object propagates through to send as described in the issue.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- api, authentication
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100