[COMPASS-7286] Access Policy is not honored Created: 02/Oct/23  Updated: 19/Oct/23  Resolved: 19/Oct/23

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

Type: Bug Priority: Major - P3
Reporter: Owen Andrew Jørgensen Assignee: Unassigned
Resolution: Incomplete Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

OS: Windows 11 x64
node.js / npm versions:
Additional info:


Attachments: Text File compass_651ab792c80bbe0a4181e6e0_log.txt    
Documentation Changes: Not Needed

 Description   

Problem Statement/Rationale

When logging in, the databases specified in the access policy are shown, but if access policy allows access to all collections under database, nothing is shown when expanding the database in Compass

Please be sure to attach relevant logs with any sensitive data redacted.
Log(s) are attached

Steps to Reproduce

Create at least two databases with at least two collections each. Create a custom access policy specifying find, insert, update, remove, createCollection for the databases, but leave the collection unspecified as to make it valid for all collections.

Expected Results

I expect Compass to enumerate the collections under each database when databases are expanded.

Actual Results

Nothing.

Additional Notes

This is a showstopper for me, but in all fairness it should be classified as Major



 Comments   
Comment by PM Bot [ 19/Oct/23 ]

There hasn't been any recent activity on this ticket, so we're resolving it. Thanks for reaching out! Please feel free to reopen this ticket if you're still experiencing the issue, and add a comment if you're able to provide more information.

Comment by PM Bot [ 11/Oct/23 ]

Hi owen.jorgensen@nhi.no! COMPASS-7286 is awaiting your response.

If this is still an issue for you, please open Jira to review the latest status and provide your feedback. Thanks!

Comment by Rhys Howell [ 03/Oct/23 ]

owen.jorgensen@nhi.no A couple of questions to help us understand the issue:

Comment by PM Bot [ 02/Oct/23 ]

Hello owen.jorgensen@nhi.no, 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:46:03 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.