[MONGOCRYPT-394] Allow on-demand credentials for KMS providers other than AWS Created: 04/Mar/22 Updated: 28/Oct/23 Resolved: 17/Mar/22 |
|
| Status: | Closed |
| Project: | Libmongocrypt |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | 1.4.0 |
| Type: | New Feature | Priority: | Unknown |
| Reporter: | Kevin Albertson | Assignee: | Kevin Albertson |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Binding Changes: | Not Needed | ||||||||
| Description |
|
Background & Motivation
On-demand credentials can be supplied by passing an empty document for "aws" in mongocrypt_setopt_kms_providers. Other KMS providers were out of scope for The proposed driver implementation of on-demand KMS providers intends to permit on-demand credentials for all KMS providers. See the conversation on this Java driver PR. Scope
|
| Comments |
| Comment by Githook User [ 17/Mar/22 ] |
|
Author: {'name': 'Kevin Albertson', 'email': 'kevin.albertson@mongodb.com', 'username': 'kevinAlbs'}Message: |