Skip to content

Clarified the hash issue further #351

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Oct 25, 2012
Merged
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
11 changes: 9 additions & 2 deletions draft/tutorial/control-access-to-mongodb-with-authentication.txt
Original file line number Diff line number Diff line change
Expand Up @@ -203,21 +203,28 @@ Given this scenario, Eve can take the hash of Alice’s password from the
{ "_id": ObjectId("507420ba032a960d16f43951"), "user": "eve", "readOnly": false, "pwd": "5dcc2819b97e68d5cfe51da6cae8a7f6" }

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

.. code-block:: javascript

use admin
db.auth("alice", "pass")

Running a ``find`` on the ``system.users`` collection:

.. code-block:: javascript

db.system.users.find()

This operation returns the following document:
shows the same password has been used and the hash is the same:

.. code-block:: javascript

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

We would like to thank Will Urbanksi, from Dell SecureWorks, for helping 10gen here.

Configuration Considerations for Authentication
-----------------------------------------------

Expand Down