MongoDB – How to Forbid Non-Authenticated Connections

mongodb

If to run mongo with authorization (i.e mongod –auth) it still allows to connect using client mongo and get to mongo cli where one will get refused to execute any command.

But I wonder if it is possible to close such connection for the unauthenticated user so one does not see mongo cli at all?

Best Answer

A new connection to MongoDB has two key aspects:

establishing a connection
authenticating the connection

As at MongoDB 3.4, the source IPs that are able to establish a connection are determined by your firewall settings. There is also a bindIp setting for MongoDB which determines which network interface(s) mongod listens to.

Once a connection is established, access control and authentication is managed by your MongoDB configuration.

In your example, you are able to connect via the mongo shell because the source IP is not blocked by firewall configuration. Assuming access control is enabled and authentication has been properly configured, establishing a connection to MongoDB does not provide any access to data.

For more information on best practices, see the MongoDB Security Checklist.

Related Solutions

MongoDB – Does Not Respect Capped Size Limit

OK, we solved this.

Issue is that mongo auto creates the collection when incoming data comes in.

So the problem was:

Drop collection
// transactions are coming in
Create collection as capped

But #3 comes too late, as the collection is already present, as not capped, because of #2.

Solution:

stop mongo
bring up mango on non standard port // to prevent auto creation of collection
create collection as capped
stop mongo, bring it back up on regular port

Now I have a capped collection!

Mongodb incremental oplog Dump not working

You are essentially attempting to dump the entire oplog and hence paging in all of it, not just the most recent data. That is going to cause a lot of IO, especially when your oplog is too large to fit into memory. On a smaller database it's not a problem because the oplog is relatively small.

The reason why it's dumping the full table is because I believe you are missing some zeroes at the end of your time:

> new Date(1452157469)
ISODate("1970-01-17T19:22:37.469Z")

I assume you wanted this:

> new Date(1452157469000)
ISODate("2016-01-07T09:04:29Z")

The speed this dump happens will depend on a number of factors, but mostly it will depend on how much data has been inserted into the oplog recently and how much of it is still in memory when you start the dump.

Best Answer

Related Solutions

MongoDB – Does Not Respect Capped Size Limit

Mongodb incremental oplog Dump not working

Related Question