[SERVER-44940] ability to use wildcards in resource field of custom role Created: 04/Dec/19  Updated: 27/Oct/23  Resolved: 04/Dec/19

Status: Closed
Project: Core Server
Component/s: None
Affects Version/s: None
Fix Version/s: None

Type: Improvement Priority: Major - P3
Reporter: Roald Osinga Assignee: Unassigned
Resolution: Community Answered Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Backwards Compatibility: Fully Compatible
Participants:

 Description   

When working for a lot of customers, it is a good idea to keep their data stored in separate databases. The software running on it will access its own tables, but requires updating of the roles of every new customer. The only solution currently would be to use the Atlas admin api, to automate this.

A much more elegant way would be if we could use a wildcard in the resource specification. For instance: `resource: {db: "customer_*", collection: "products"}, action: ["find"]`.



 Comments   
Comment by Dmitry Agranat [ 04/Dec/19 ]

Hi roald@shoppingminds.com,

The SERVER project is for bugs and feature suggestions for the MongoDB server. To inform our Atlas team of issues you are having or feature requests you'd like to suggest, please reach out to the Atlas support team via Intercom. You can do this by clicking the round green button at the bottom right of the cluster view page in Atlas.

Regards,
Dima

Generated at Thu Feb 08 05:07:25 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.