Authentication mechanisms in MongoDB

Introduction

Authentication mechanisms help verify who you are before you can use a database. This keeps data safe and private.

When you want to control who can see or change your data.

When multiple people or apps use the same database and need different access levels.

When you want to protect sensitive information from strangers.

When you connect to a database over the internet and need to be sure the user is trusted.

Syntax

MongoDB

db.auth(username, password)

This command is used inside the MongoDB shell to log in as a user.

You must have created the user with a username and password before using this.

Examples

This tries to log in as user 'alice' with the password 'mypassword'.

MongoDB

db.auth('alice', 'mypassword')

This tries to log in as user 'bob' with the password '12345'.

MongoDB

db.auth('bob', '12345')

Sample Program

This example first creates a user named 'testUser' with password 'testPass' and read/write access. Then it logs in as that user.

MongoDB

use admin
// Create a user
db.createUser({user: 'testUser', pwd: 'testPass', roles: ['readWrite']})

// Authenticate as the new user
db.auth('testUser', 'testPass')

Important Notes

Authentication must be enabled in MongoDB configuration to work.

Passwords are stored securely, so you cannot see them after creation.

Use roles to control what authenticated users can do.

Summary

Authentication checks who you are before allowing database access.

Use db.auth() to log in with a username and password.

Always create users with proper roles to keep data safe.

Practice

1. What is the main purpose of authentication in MongoDB?

easy

A. To create indexes on collections

B. To backup the database automatically

C. To optimize query performance

D. To verify the identity of a user before granting access

Solution

1. Step 1: Understand authentication concept

   Authentication means checking who you are before allowing access.

2. Step 2: Identify the purpose in MongoDB

   MongoDB uses authentication to verify user identity to protect data.

3. Final Answer:

   To verify the identity of a user before granting access -> Option D

4. Quick Check:

   Authentication = Verify identity [OK]

Hint: Authentication means checking who you are [OK]

Common Mistakes:

• Confusing authentication with backup
• Thinking authentication improves query speed
• Mixing authentication with indexing

2. Which of the following is the correct syntax to authenticate a user in MongoDB shell?

easy

A. db.auth('username', 'password')

B. db.authenticate('username', 'password')

C. db.login('username', 'password')

D. db.userAuth('username', 'password')

Solution

1. Step 1: Recall MongoDB authentication method

   The correct method to authenticate is db.auth().

2. Step 2: Match syntax with options

   Only db.auth('username', 'password') matches the correct syntax.

3. Final Answer:

   db.auth('username', 'password') -> Option A

4. Quick Check:

   Authenticate = db.auth() [OK]

Hint: Use db.auth() to log in with username and password [OK]

Common Mistakes:

• Using db.authenticate() which does not exist
• Using db.login() which is invalid
• Confusing method names with userAuth()

3. Consider this MongoDB shell command sequence:

use admin
var result = db.auth('alice', 'mypassword')

What will be the value of result if authentication succeeds?

medium

A. 1

B. false

C. true

D. null

Solution

1. Step 1: Understand db.auth() return value

   When authentication succeeds, db.auth() returns 1.

2. Step 2: Match return value with options

   Only 1 matches the expected numeric return value.

3. Final Answer:

   1 -> Option A

4. Quick Check:

   Success returns 1 [OK]

Hint: db.auth() returns 1 if login works [OK]

Common Mistakes:

• Expecting boolean true instead of numeric 1
• Thinking it returns false on success
• Assuming it returns null or undefined

4. You run db.auth('bob', 'wrongpass') but it always returns 1. What is the most likely cause?

medium

A. The user 'bob' does not exist

B. The password is case-insensitive

C. You are already authenticated as 'bob' or another user

D. MongoDB does not check passwords

Solution

1. Step 1: Understand db.auth() behavior when already logged in

   If already authenticated, db.auth() returns 1 without rechecking password.

2. Step 2: Analyze why wrong password still returns 1

   This happens because the session is already authenticated as 'bob' or another user.

3. Final Answer:

   You are already authenticated as 'bob' or another user -> Option C

4. Quick Check:

   Already logged in means db.auth() returns 1 [OK]

Hint: db.auth() returns 1 if already logged in [OK]

Common Mistakes:

• Assuming wrong password always returns false
• Thinking MongoDB ignores passwords
• Believing user must exist for true return

5. You want to create a user with read-only access to the sales database. Which command correctly creates this user with proper authentication roles?

hard

A. db.addUser('readonly', 'pass123', 'read')

B. db.createUser({user: 'readonly', pwd: 'pass123', roles: [{role: 'read', db: 'sales'}]})

C. db.createUser({username: 'readonly', password: 'pass123', roles: ['read']})

D. db.createUser({user: 'readonly', pwd: 'pass123', roles: ['readWrite']})

Solution

1. Step 1: Identify correct syntax for creating user with roles

   The correct syntax uses db.createUser() with user, pwd, and roles as an array of objects specifying role and database.

2. Step 2: Match read-only role on 'sales' database

   db.createUser({user: 'readonly', pwd: 'pass123', roles: [{role: 'read', db: 'sales'}]}) correctly assigns role 'read' on database 'sales'.

3. Final Answer:

   db.createUser({user: 'readonly', pwd: 'pass123', roles: [{role: 'read', db: 'sales'}]}) -> Option B

4. Quick Check:

   Create user with roles array = db.createUser({user: 'readonly', pwd: 'pass123', roles: [{role: 'read', db: 'sales'}]}) [OK]

Hint: Use db.createUser() with roles array for access control [OK]

Common Mistakes:

• Using deprecated db.addUser() method
• Incorrect field names like username instead of user
• Assigning wrong roles like readWrite for read-only access