[COMPASS-5691] Connected to Atlas Cluster but it shows empty database Created: 05/Apr/22 Updated: 29/Oct/23 Resolved: 07/Apr/22 |
|
| Status: | Closed |
| Project: | Compass |
| Component/s: | Data, Users |
| Affects Version/s: | 1.29.6, 1.30.1, 1.31.1 |
| Fix Version/s: | 1.31.2 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Blaise Crisologo (Inactive) | Assignee: | Rhys Howell |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Environment: |
Windows 10 |
||
| Attachments: |
|
||||||||||||||||
| Issue Links: |
|
||||||||||||||||
| Documentation Changes: | Not Needed | ||||||||||||||||
| Sprint: | Iteration Yonkers | ||||||||||||||||
| Description |
Problem Statement/RationaleI have a customer on intercom who reported the incident: They were able establish connection using Compass to their M2 cluster carpediemxp-test-0000001, but it shows an empty DB content as per the first image. However, checking their Atlas DE shows that there should be DB content, which is not reflected on Compass as shown in the second image.
The current DB user role they have has the following permissions:
I've attached the logs obtained from the version 1.31.1 Compass trial in text format. However, they are not encountering the same issue when connecting to a different cluster, in particular this M0 Cluster0 that's on a different Atlas Organization. They can view it as per below:
Similar incident reported on this slack thread under #compass channel. Steps to ReproduceSetting a DB user with only "specific privileges" and no role for the admin DB such as below:
I don't see any DB content either for even the specific DB and collections allowed for the DB user above:
Expected ResultsDB Content should be shown given the appropriate DB user role and permissions. Actual ResultsCompass is not showing the DB content for their M2 cluster. Additional NotesAsked the customer above to try Compass 1.29.6 and 1.31.0 and 1.30.1 and they mentioned they encounter the same errors. |
| Comments |
| Comment by Githook User [ 19/Apr/22 ] |
|
Author: {'name': 'Rhys', 'email': 'Anemy@users.noreply.github.com', 'username': 'Anemy'}Message: fix(data-service): use databases where user has built in roles in listDatabases |
| Comment by Githook User [ 11/Apr/22 ] |
|
Author: {'name': 'Rhys', 'email': 'Anemy@users.noreply.github.com', 'username': 'Anemy'}Message: fix(data-service): use databases where user has built in roles in listDatabases |
| Comment by Rhys Howell [ 11/Apr/22 ] |
|
will.huang@mongodb.com blaise.crisologo@mongodb.com We've just published Compass `v1.31.2-beta.5` with a partial workaround for this issue which will fix listing databases for users with limited built in roles on shared tier clusters. While hopefully this workaround will cover most general use cases, as well as the case in this ticket, this is a partial workaround. This is partial because, without being able to retrieve the privileges for a certain user, we can currently only derive a user's permissions from the built in roles that users have. For permissions stemming from privileges given by custom roles we'll have to wait for a fix to be deployed on the Atlas side of things. So that will start working one day without a Compass release. That work is tracked here: https://jira.mongodb.org/browse/CLOUDP-118942 |
| Comment by Githook User [ 11/Apr/22 ] |
|
Author: {'name': 'Rhys', 'email': 'Anemy@users.noreply.github.com', 'username': 'Anemy'}Message: fix(data-service): use databases where user has built in roles in listDatabases |
| Comment by Githook User [ 08/Apr/22 ] |
|
Author: {'name': 'Rhys', 'email': 'Anemy@users.noreply.github.com', 'username': 'Anemy'}Message: fix(data-service): use databases where user has built in roles in listDatabases |
| Comment by Githook User [ 08/Apr/22 ] |
|
Author: {'name': 'Rhys', 'email': 'Anemy@users.noreply.github.com', 'username': 'Anemy'}Message: fix(data-service): use databases where user has built in roles in listDatabases |
| Comment by Githook User [ 07/Apr/22 ] |
|
Author: {'name': 'Rhys', 'email': 'Anemy@users.noreply.github.com', 'username': 'Anemy'}Message: fix(data-service): use databases where user has built in roles in listDatabases |
| Comment by Githook User [ 07/Apr/22 ] |
|
Author: {'name': 'Rhys', 'email': 'Anemy@users.noreply.github.com', 'username': 'Anemy'}Message: fix(data-service): use databases where user has built in roles in listDatabases |
| Comment by Githook User [ 07/Apr/22 ] |
|
Author: {'name': 'Rhys', 'email': 'Anemy@users.noreply.github.com', 'username': 'Anemy'}Message: fix(data-service): use databases where user has built in roles in listDatabases |
| Comment by Githook User [ 07/Apr/22 ] |
|
Author: {'name': 'Rhys', 'email': 'Anemy@users.noreply.github.com', 'username': 'Anemy'}Message: Merge branch 'main' into |
| Comment by Githook User [ 07/Apr/22 ] |
|
Author: {'name': 'Le Roux Bodenstein', 'email': 'lerouxb@gmail.com', 'username': 'lerouxb'}Message: Merge branch 'main' into |