requests-compatible signer
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 30/100
- Issue type
- Feature
- Clarity
- Mostly clear
- Activity status
- Stale
- Tech stack
- python
- Domain
- api, authentication
Research direction
Start by reading the linked botocore issue and the CRT Python signing interfaces, then compare them with the requests auth interface. The change is complete when a requests.Request can receive SigV4 headers through a compatible function without adding requests as a dependency.
Written by the indexing model from the issue text.
Description
This is a long-standing feature request of botocore: https://github.com/boto/botocore/issues/1784
Both botocore and this project use custom HTTP request representation, and the signing mechanism works against this custom representation. This makes it difficult to SigV4 sign an arbitrary request using the most-commonly and -recommended HTTP library requests, which is necessary when using API Gateway with IAM authentication.
The CRT bindings should provide a function compatible with the requests auth interface (that is, it takes a requests.Request and adds the SigV4 headers). This function could then be exposed by higher-level interfaces (e.g., boto3) without needing to translate a requests.Request into the CRT's custom HTTP request representation. I think this should be doable without adding a dependency on requests.
- Dominant language
- Python
- Stars
- 101
- Forks
- 58
- Avg merge
- 10h 24m
- Merged PRs (30d)
- 3
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 awslabs/aws-crt-python
-
bug needs-triage
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
awslabs/aws-crt-python#760 · 2 comments ·
-
AIO HTTP/2 writer task raises unhandled AWS_ERROR_HTTP_STREAM_HAS_COMPLETED during normal shutdown Open
Difficulty 3/5 1-2 days Newbie friendliness 72/100
awslabs/aws-crt-python#762 ·
-
bug needs-triage
Difficulty 4/5 3-5 days Newbie friendliness 35/100
awslabs/aws-crt-python#703 · 1 comment ·
-
bug needs-triage
Difficulty 4/5 3-5 days Newbie friendliness 45/100
awslabs/aws-crt-python#699 · 2 comments ·
-
bug needs-triage potential-regression
Difficulty 4/5 3-5 days Newbie friendliness 35/100
awslabs/aws-crt-python#693 · 1 comment ·
All issues in awslabs/aws-crt-python
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
-
enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 74/100