[MONGOCRYPT-259] Generalize kms_request_t Created: 03/Aug/20 Updated: 28/Oct/23 Resolved: 19/Aug/20 |
|
| Status: | Closed |
| Project: | Libmongocrypt |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | 1.1.0-beta1 |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Kevin Albertson | Assignee: | Kevin Albertson |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Epic Link: | MONGOCRYPT-250 |
| Description |
|
Currently generating and using a kms_request_t has some AWS specific logic. Constructing with kms_request_new automatically adds an X-Amz-Date header. And there is no way to obtain an HTTP request without the AWS signature. Goal: Make kms_request_t general enough to send non-AWS specific HTTP requests. This will to make it usable for Azure auth and the REST API. |
| Comments |
| Comment by Githook User [ 19/Aug/20 ] |
|
Author: {'name': 'Kevin Albertson', 'email': 'kevin.albertson@mongodb.com', 'username': 'kevinAlbs'}Message:
|