[COMPASS-3562] Can't connect to DB in Atlas when user can't list databases and collections Created: 12/Apr/19 Updated: 14/Dec/21 |
|
| Status: | Open |
| Project: | Compass |
| Component/s: | Connectivity |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | New Feature | Priority: | Major - P3 |
| Reporter: | Massimiliano Marcon | Assignee: | Unassigned |
| Resolution: | Unresolved | Votes: | 1 |
| Labels: | internal | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Attachments: |
|
||||||||||||
| Issue Links: |
|
||||||||||||
| Description |
|
This was reported by a user at MongoDB.local Berlin. When connecting to an Atlas cluster where the user does not have any permissions to list databases/collections Compass is not really useful. Attached are screenshots of the role definition in Atlas and the corresponding error in Compass. Solution proposed by user: additional field in the connect screen do define what database to use, in addition to what auth database to use. |