[SERVER-41370] Handle AWS KMS errors cleanly for FLE shell Created: 29/May/19 Updated: 29/Oct/23 Resolved: 03/Jun/19 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | 4.1.14 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Shreyas Kalyan | Assignee: | Roxane Fruytier (Inactive) |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||
| Backwards Compatibility: | Fully Compatible | ||||
| Operating System: | ALL | ||||
| Sprint: | Security 2019-06-03 | ||||
| Participants: | |||||
| Linked BF Score: | 0 | ||||
| Description |
|
Currently, KMS errors return an IDL parsing error, which is not a useful message to the user. |
| Comments |
| Comment by Githook User [ 03/Jun/19 ] | ||||
|
Author: {'name': 'Mark Benvenuto', 'email': 'mark.benvenuto@mongodb.com', 'username': 'markbenvenuto'}Message: | ||||
| Comment by Githook User [ 03/Jun/19 ] | ||||
|
Author: {'name': 'Roxane', 'email': 'roxane.fruytier@10gen.com'}Message: | ||||
| Comment by Mark Benvenuto [ 30/May/19 ] | ||||
|
When a JSON response is received from AWS, it may either be the expected response or an error. Errors are returned as
We should first check if a response is an error by testing the JSON response for the existence of "__type" field and if it is an error, decode it as an error message and then raise it as a uassert. |