[COMPASS-5930] Connection with in-use encryption enabled but no KMS provider hangs Compass window Created: 05/Jul/22 Updated: 29/Oct/23 Resolved: 24/Aug/22 |
|
| Status: | Closed |
| Project: | Compass |
| Component/s: | Field Level Encryption |
| Affects Version/s: | None |
| Fix Version/s: | 1.33.1 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Sergey Petushkov | Assignee: | Anna Henningsen |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Documentation Changes: | Not Needed |
| Sprint: | Iteration Fish, Iteration Grouper, Iteration Herring, Iteration Isopod |
| Description |
Problem Statement/RationaleIf you connect to a cluster with in-use connection without storing the provider key (the recommended and default behavior) and then re use the saved connection (either from recents or favorited connection), you'll be able to connect with in-use encryption being in a weird state, leading to any attempt at fetching documents for a collection that has encryption hanging Compass window forever. See this thread for some additional context Steps to Reproduce
Expected Results
Actual Results
Additional NotesSeems like validation for the KMS providers kicks in only when you start editing the fields, maybe that's true for other fields too? We probably want the validation to not be coupled just to editing fields in the form |
| Comments |
| Comment by Githook User [ 28/Sep/22 ] |
|
Author: {'name': 'Anna Henningsen', 'email': 'anna.henningsen@mongodb.com', 'username': 'addaleax'}Message: fix(data-service): fully remove empty KMS provider options Fully remove KMS providers from the list of providers if their |
| Comment by Githook User [ 31/Aug/22 ] |
|
Author: {'name': 'Anna Henningsen', 'email': 'anna.henningsen@mongodb.com', 'username': 'addaleax'}Message: fix(data-service): fully remove empty KMS provider options Fully remove KMS providers from the list of providers if their |
| Comment by Githook User [ 30/Aug/22 ] |
|
Author: {'name': 'Anna Henningsen', 'email': 'anna.henningsen@mongodb.com', 'username': 'addaleax'}Message: fix(data-service): fully remove empty KMS provider options Fully remove KMS providers from the list of providers if their |
| Comment by Githook User [ 29/Aug/22 ] |
|
Author: {'name': 'Anna Henningsen', 'email': 'anna.henningsen@mongodb.com', 'username': 'addaleax'}Message: fix(data-service): fully remove empty KMS provider options Fully remove KMS providers from the list of providers if their |
| Comment by Githook User [ 26/Aug/22 ] |
|
Author: {'name': 'Anna Henningsen', 'email': 'anna.henningsen@mongodb.com', 'username': 'addaleax'}Message: fix(data-service): fully remove empty KMS provider options Fully remove KMS providers from the list of providers if their |
| Comment by Githook User [ 24/Aug/22 ] |
|
Author: {'name': 'Anna Henningsen', 'email': 'anna.henningsen@mongodb.com', 'username': 'addaleax'}Message: fix(data-service): fully remove empty KMS provider options Fully remove KMS providers from the list of providers if their |
| Comment by Githook User [ 23/Aug/22 ] |
|
Author: {'name': 'Anna Henningsen', 'email': 'anna@addaleax.net', 'username': 'addaleax'}Message: fix(data-service): fully remove empty KMS provider options Fully remove KMS providers from the list of providers if their |
| Comment by Anna Henningsen [ 23/Aug/22 ] |
|
First note while looking into this: This only reproduced for me with a Local KMS, not AWS. |