Closed christiangroth closed 5 years ago
In upcoming rh4 the config database is hidden (since it is more an MongoDB internal resource)
I'm going to fix this in rh3 as well
fixed in 3148ba612b313ddb303f0475a24be84e76d10143
@mkjsix please release 3.10.1
closing this one. @christiangroth feel free to reopen if you find any issue.
RESTHeart 3.10.1 has been released.
https://github.com/SoftInstigate/restheart/releases/tag/3.10.1
Hi,
we're currently in a situation using RH 3.9.0 and MongoDB 3.4.x and we're upgrading MongoDB to 3.6.x. During the process we encountered some issues related to the MongoDB 'config' database. In version 3.4.x this database was only used for sharded clusters, which we don't have. Starting with version 3.6.x it's also used for some other features and when bootstrapping a clean new MongoDB in version 3.6.x the config database will be created.
This leads us to the following issues we ran into:
Nevertheless the config database is still returned / accessible when requesting root / listing databases:
At this point I'm not sure what would be the best solution. From our point of view the 'config' database is an internal database relevant for MongoDB only and should not be exposed, as it is done with the local database. This might be kind of a "bug" in RH. Otherwise an option blacklisting databases might be helpful to attack this in a more generic way.
Hint: We are not able to use mongo-mounts because the number and names of the MongoDB databases in our environment is dynamic, so we can't whitelist databases using mongo-mounts.