[COMPASS-3173] collection-level read-only users only see collection on sidebar Created: 04/Oct/18  Updated: 27/Oct/23  Resolved: 17/Sep/22

Status: Closed
Project: Compass
Component/s: DDL
Affects Version/s: 1.16.0
Fix Version/s: No version

Type: Task Priority: Major - P3
Reporter: Anna Herlihy (Inactive) Assignee: Unassigned
Resolution: Gone away Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Attachments: PNG File ReadDBuser_TestforCompass1.png     PNG File ReadDBuser_TestforCompass2.png     PNG File ReadDBuser_TestforCompass_Betav126.png     PNG File ReadDBuser_TestforCompass_v125.png     PNG File ReadDBuser_TestforCompass_v125_mongosh.png     PNG File Screen Shot 2018-10-04 at 11.44.55 AM.png     PNG File intercomChat_36687801319520_1 (1).png     PNG File intercomChat_36687801319520_2 (1).png    
Issue Links:
Related
is related to COMPASS-3180 Read-only users on M0 Atlas clusters ... Closed
Documentation Changes: Not Needed

 Description   

For a read-only user with access to only one connection, the collection shows up in the sidebar but the collection tab itself is empty.



 Comments   
Comment by Maurizio Casimirri [ 17/Sep/22 ]

was already fixed

Comment by Julia Jen [ 05/Mar/21 ]

See slack thread for customer issue and employee testing done, linked intercom chat above. 

  • Note the linked chat and thread is related to customer use case where they wish to:
    • connect to their cluster using a configured Atlas built-in role Read DB user scoped to specific db and associated collection(s)
    • view documents in collection using Compass

  - Currently the customer_cannot see any collection(s_) in Compass sidebar (showing as 0) and also on the main navigation they see the DB namespace but no collections

    • As a temporary workaround, customer was directed to use mongo shell, but customer wishes to use Compass to see data in graphical user interface (not the built-in MongoSH component)
    • Internal testing done shows that the same behavior surfacing when using any of the Compass stable and beta version
    • Inquiring as to whether this is due to command listCollections (see listed permissions for read DB user) being unavailable for the DB user 'read' privileges which in turn is affecting the collection view access in Compass ?
Generated at Wed Feb 07 22:32:22 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.