Skip to content

Commit 154f62f

Browse files
author
markofu
committed
Clarified the hash issue further
1 parent 6689385 commit 154f62f

File tree

1 file changed

+9
-2
lines changed

1 file changed

+9
-2
lines changed

draft/tutorial/control-access-to-mongodb-with-authentication.txt

Lines changed: 9 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -203,21 +203,28 @@ Given this scenario, Eve can take the hash of Alice’s password from the
203203
{ "_id": ObjectId("507420ba032a960d16f43951"), "user": "eve", "readOnly": false, "pwd": "5dcc2819b97e68d5cfe51da6cae8a7f6" }
204204

205205
Alice has read and write accounts on both ``db1`` and ``db2`` and
206-
also has access on the ``admin`` database. Consider the following:
206+
also has access on the ``admin`` database. Consider the following
207+
example where Alice authenticates to the ``admin`` db:
207208

208209
.. code-block:: javascript
209210

210211
use admin
211212
db.auth("alice", "pass")
212213

214+
Running a ``find`` on the ``system.users`` collection:
215+
216+
.. code-block:: javascript
217+
213218
db.system.users.find()
214219

215-
This operation returns the following document:
220+
shows the same password has been used and the hash is the same:
216221

217222
.. code-block:: javascript
218223

219224
{ "_id": ObjectId("50742045032a960d16f43950"), "user": "alice", "readOnly": false, "pwd": "ac2061b4a08ef8f2d60a07dc18ab4a0a" }
220225

226+
We would like to thank Will Urbanksi, from Dell SecureWorks, for helping 10gen here.
227+
221228
Configuration Considerations for Authentication
222229
-----------------------------------------------
223230

0 commit comments

Comments
 (0)