Local strategy (username/password) in NestJS - Performance & Optimization

Performance: Local strategy (username/password)

MEDIUM IMPACT

This affects the server-side authentication process speed and the responsiveness of login interactions.

Authenticating users with username and password

NestJS

async validate(username: string, password: string) {
  const user = await this.userService.findByUsername(username);
  if (!user) return null;
  const isValid = await bcrypt.compare(password, user.password);
  if (!isValid) return null;
  return user;
}
// Additionally, use caching or rate limiting to reduce repeated DB calls

Using async bcrypt.compare prevents blocking; caching user data reduces DB calls, improving responsiveness.

📈 Performance GainNon-blocking password check and fewer DB queries reduce login delay by up to 70ms

Authenticating users with username and password

NestJS

async validate(username: string, password: string) {
  const user = await this.userService.findByUsername(username);
  if (!user) return null;
  const isValid = bcrypt.compareSync(password, user.password);
  if (!isValid) return null;
  return user;
}

This pattern performs password hashing comparison synchronously inside the request cycle, blocking event loop and delaying response.

📉 Performance CostBlocks event loop for password hash comparison, increasing login latency by 50-100ms per request

Performance Comparison

Pattern	Server CPU Usage	Response Delay	Blocking Behavior	Verdict
Synchronous password hash check	High CPU blocking	Increases by 50-100ms	Blocks event loop	[X] Bad
Asynchronous bcrypt.compare with caching	Lower CPU blocking	Minimal delay added	Non-blocking	[OK] Good

Rendering Pipeline

The local strategy runs on the server before the page renders. It affects how fast the server responds to login requests, impacting the time until the user sees the authenticated page.

→Server Processing

→Network Response

→Client Rendering

⚠️ BottleneckServer Processing during password hash comparison

Core Web Vital Affected

INP

This affects the server-side authentication process speed and the responsiveness of login interactions.

Optimization Tips

1Always use asynchronous password hashing to avoid blocking the server.

2Cache user data when possible to reduce database calls during login.

3Monitor server response times for login requests to catch performance issues early.

Performance Quiz - 3 Questions

What is the main performance issue with synchronous password hashing in local strategy?

A It causes layout shifts on the page

B It blocks the server event loop, increasing login delay

C It increases client-side rendering time

D It reduces network bandwidth

DevTools: Network

How to check: Open DevTools, go to Network tab, filter login request, and check the time taken for the request to complete.

What to look for: Look for long server response times during login indicating slow authentication processing.

Practice

1. What is the main purpose of the LocalStrategy in NestJS authentication?

easy

A. To encrypt user passwords

B. To generate JWT tokens for users

C. To handle user registration

D. To verify username and password for user login

Solution

1. Step 1: Understand the role of LocalStrategy

   The LocalStrategy is designed to check user credentials, specifically username and password, during login.

2. Step 2: Differentiate from other strategies

   Unlike JWT or OAuth strategies, LocalStrategy focuses on validating credentials, not token generation or registration.

3. Final Answer:

   To verify username and password for user login -> Option D

4. Quick Check:

   LocalStrategy = username/password check [OK]

Hint: Local strategy always checks username and password [OK]

Common Mistakes:

• Confusing LocalStrategy with JWT token generation
• Thinking LocalStrategy handles user registration
• Assuming LocalStrategy encrypts passwords

2. Which method must be implemented in a NestJS LocalStrategy class to check user credentials?

easy

A. authenticate()

B. validate()

C. login()

D. verify()

Solution

1. Step 1: Recall LocalStrategy method names

   In NestJS, the LocalStrategy requires a validate method to check username and password.

2. Step 2: Confirm method purpose

   The validate method returns the user if credentials are correct or throws an error if not.

3. Final Answer:

   validate() -> Option B

4. Quick Check:

   Credential check method = validate() [OK]

Hint: LocalStrategy uses validate() to check credentials [OK]

Common Mistakes:

• Using authenticate() which is not a LocalStrategy method
• Confusing login() with validate()
• Assuming verify() is required

3. Given this LocalStrategy snippet, what happens if the password is incorrect?

async validate(username: string, password: string) {
  const user = await this.authService.validateUser(username, password);
  if (!user) {
    throw new UnauthorizedException();
  }
  return user;
}

medium

A. The function returns null silently

B. The user object is returned anyway

C. An UnauthorizedException is thrown stopping login

D. The password is reset automatically

Solution

1. Step 1: Analyze the validate method logic

   If validateUser returns no user (password incorrect), the code throws UnauthorizedException.

2. Step 2: Understand exception effect

   Throwing UnauthorizedException stops the login process and signals failure.

3. Final Answer:

   An UnauthorizedException is thrown stopping login -> Option C

4. Quick Check:

   Wrong password = UnauthorizedException thrown [OK]

Hint: Throw UnauthorizedException if user not found [OK]

Common Mistakes:

• Assuming user is returned even if password is wrong
• Thinking function returns null without error
• Believing password resets automatically

4. Identify the error in this LocalStrategy validate method:

async validate(username: string, password: string) {
  const user = this.authService.validateUser(username, password);
  if (!user) {
    throw new UnauthorizedException();
  }
  return user;
}

medium

A. Missing await before authService.validateUser call

B. UnauthorizedException should not be thrown

C. validate method should not be async

D. username and password parameters are reversed

Solution

1. Step 1: Check async call usage

   The method calls validateUser which returns a Promise, but lacks await.

2. Step 2: Understand consequences of missing await

   Without await, user is a Promise, so if (!user) check is incorrect and login logic breaks.

3. Final Answer:

   Missing await before authService.validateUser call -> Option A

4. Quick Check:

   Async calls need await to get results [OK]

Hint: Always await async calls in validate() [OK]

Common Mistakes:

• Forgetting await on async service calls
• Throwing exceptions incorrectly
• Misordering parameters

5. You want to customize the LocalStrategy to allow login with either username or email. Which change is best to implement in the validate method?

hard

A. Modify validateUser to accept a single identifier and check both username and email

B. Add a second validate method for email login

C. Use two separate LocalStrategy classes for username and email

D. Change the password parameter to accept email instead

Solution

1. Step 1: Understand the goal

   Allow login by username or email using one validate method.

2. Step 2: Best approach

   Modify validateUser to accept one identifier and check if it matches username or email, then verify password.

3. Step 3: Why other options fail

   Adding multiple validate methods or strategies complicates logic; changing password parameter is incorrect.

4. Final Answer:

   Modify validateUser to accept a single identifier and check both username and email -> Option A

5. Quick Check:

   One validate method, flexible identifier [OK]

Hint: Use one validate method checking username or email [OK]

Common Mistakes:

• Creating multiple validate methods unnecessarily
• Using separate strategies for username and email
• Confusing password parameter with identifier