Authentication mechanisms in MongoDB - Time & Space Complexity

Time Complexity: Authentication mechanisms

O(n)

Understanding Time Complexity

When we check how fast authentication works in MongoDB, we want to know how the time it takes changes as more users or requests happen.

We ask: How does the system handle more login attempts or more users trying to connect?

Scenario Under Consideration

Analyze the time complexity of the following MongoDB authentication check.

// Simplified authentication check
const user = db.users.findOne({ username: inputUsername });
if (user) {
  if (user.passwordHash === hash(inputPassword)) {
    return 'Authenticated';
  } else {
    return 'Wrong password';
  }
} else {
  return 'User not found';
}
    

This code looks up a user by username and checks if the password matches.

Identify Repeating Operations

Identify the loops, recursion, array traversals that repeat.

• Primary operation: Searching the user collection for a matching username.
• How many times: Once per authentication attempt.

How Execution Grows With Input

As the number of users grows, the time to find a user depends on how the database searches.

Input Size (n)	Approx. Operations
10	About 10 checks if no index
100	About 100 checks if no index
1000	About 1000 checks if no index

Pattern observation: Without an index, the search time grows directly with the number of users.

Final Time Complexity

Time Complexity: O(n)

This means the time to authenticate grows in a straight line as more users are added if no special search method is used.

Common Mistake

[X] Wrong: "Authentication time stays the same no matter how many users exist."

[OK] Correct: Without an index, the database must check many users one by one, so more users mean more time.

Interview Connect

Understanding how authentication time changes with user count helps you explain real system behavior clearly and shows you know how databases work under the hood.

Self-Check

"What if we add an index on the username field? How would the time complexity change?"

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