[COMPASS-7258] User with Custom Role having @db_name(all collections) doesn't see collections Created: 25/Sep/23  Updated: 27/Oct/23  Resolved: 25/Sep/23

Status: Closed
Project: Compass
Component/s: None
Affects Version/s: 1.39.4
Fix Version/s: No version

Type: Bug Priority: Minor - P4
Reporter: Alexandre VS Assignee: Rhys Howell
Resolution: Works as Designed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

OS:

  • Compass on Windows 10
  • db is free plan

Issue Links:
Problem/Incident
Related
is related to COMPASS-5691 Connected to Atlas Cluster but it sho... Closed
Documentation Changes: Not Needed

 Description   

Problem Statement/Rationale

If we connect with a user having a custom role with only "(find, insert, remove, etc) @db_name(all collections)" permission, Compass won't show any collection available in the database. I confirmed the user had the permission through c# db calls using it. But for Compass to display the collections, we need to add every one of them manually instead of "all collections".

Steps to Reproduce

  • create a new custom role
  • add "(find, insert, remove, etc) @db_name(all collections)" permission for a database containing collections to this custom role
    * create a new user, with this custom role
  • connect to compass with the new user

Expected Results

All the db collections should be displayed.

Actual Results

Collections won't be displayed.



 Comments   
Comment by Rhys Howell [ 25/Sep/23 ]

Hi alexandre.vosv@gmail.com Looks like this is a bug with how the list collections command with custom roles is being handled with the M0 (free plan) in Atlas. I've created a new ticket  https://jira.mongodb.org/browse/CLOUDP-201862 to track that. Going to close this one as it isn't something we can fix inside of Compass.

Thanks for reporting the issue! Hopefully we can get it sorted for you soon.

Comment by PM Bot [ 25/Sep/23 ]

Hello alexandre.vosv@gmail.com, thank you for reaching out to us! The team will review your issue and get back to you soon as soon as possible.

Please review your issue to ensure you've included your environment details and have attached relevant logs (with any sensitive data redacted), so that we're best able to provide you a timely and thorough response. Thanks again!

Generated at Wed Feb 07 22:45:57 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.