Why authentication needs server-side logic in Astro - See It in Action

Why Authentication Needs Server-Side Logic

📖 Scenario: You are building a simple website that requires users to log in to see their personal dashboard. You want to understand why some parts of the login process must happen on the server, not just in the browser.

🎯 Goal: Create a small Astro project that shows a login form and uses server-side logic to check the username and password securely.

📋 What You'll Learn

Create a user data object with a username and password

Add a variable to hold the login status

Write a server-side function to check the login credentials

Use the server-side function in the Astro component to show login success or failure

💡 Why This Matters

🌍 Real World

Websites need to check user identity safely to protect private information and prevent unauthorized access.

💼 Career

Understanding server-side authentication is essential for web developers to build secure applications.

1

Create user data object

Create a constant called userData with the exact object { username: 'astroUser', password: 'securePass123' }.

Astro

# Create a constant called userData with username and password
# Your code here

Hint

Think of userData as a small box holding the username and password.

2

Add login status variable

Create a variable called isLoggedIn and set it to false to track if the user is logged in.

Astro

const userData = { username: 'astroUser', password: 'securePass123' };
# Create a variable called isLoggedIn and set it to false
# Your code here

Hint

This variable will help us remember if the user has logged in successfully.

3

Write server-side login check function

Write an async function called checkLogin that takes username and password as parameters and returns true if they match userData, otherwise false. Use strict equality checks.

Astro

const userData = { username: 'astroUser', password: 'securePass123' };
let isLoggedIn = false;
# Write async function checkLogin(username, password) to compare with userData
# Your code here

Hint

This function simulates checking the username and password on the server securely.

4

Use server-side function in Astro component

In the Astro component, call checkLogin with 'astroUser' and 'securePass123'. Set isLoggedIn to the result. Then, add a conditional to show <p>Welcome back!</p> if isLoggedIn is true, or <p>Login failed.</p> if false.

Astro

const userData = { username: 'astroUser', password: 'securePass123' };
let isLoggedIn = false;

async function checkLogin(username, password) {
  return username === userData.username && password === userData.password;
}

// Call checkLogin and set isLoggedIn
// Add conditional rendering to show welcome or failure message
# Your code here

Hint

This step shows how the server checks the login and the page shows the right message.

Practice

1. Why is authentication usually handled on the server side in web applications?

easy

A. Because authentication does not need any security

B. Because the server can securely check user credentials and control access

C. Because the client can decide who is allowed without server help

D. Because the client can store passwords safely

Solution

1. Step 1: Understand the role of server in authentication

   The server securely stores user data and verifies credentials to protect sensitive information.

2. Step 2: Recognize client limitations

   The client cannot be trusted to securely store or verify credentials because it can be manipulated.

3. Final Answer:

   Because the server can securely check user credentials and control access -> Option B

4. Quick Check:

   Server handles security = D [OK]

Hint: Server controls access securely, client just sends info [OK]

Common Mistakes:

• Thinking client can safely store passwords
• Believing client can decide access alone
• Ignoring security risks on client side

2. Which of the following is the correct way to send user login data from client to server in Astro?

easy

A. fetch('/login', { method: 'GET', body: JSON.stringify({username, password}) })

B. fetch('/login', { method: 'POST', body: username + password })

C. fetch('/login', { method: 'POST', body: JSON.stringify({username, password}) })

D. fetch('/login', { method: 'POST' })

Solution

1. Step 1: Identify correct HTTP method for sending login data

   Login data should be sent using POST to keep data in the request body, not URL.

2. Step 2: Check data format in request body

   Data should be JSON stringified for proper parsing on server side.

3. Final Answer:

   fetch('/login', { method: 'POST', body: JSON.stringify({username, password}) }) -> Option C

4. Quick Check:

   POST with JSON body = B [OK]

Hint: Use POST and JSON.stringify for login data [OK]

Common Mistakes:

• Using GET method which exposes data in URL
• Sending raw concatenated strings instead of JSON
• Omitting the request body

3. Given this Astro server code snippet handling login:

export async function post({ request }) {
  const { username, password } = await request.json();
  if (username === 'user' && password === 'pass') {
    return new Response('Success', { status: 200 });
  } else {
    return new Response('Fail', { status: 401 });
  }
}

What will the server respond if the client sends username='user' and password='wrong'?

medium

A. Fail with status 401

B. Success with status 200

C. Error with status 500

D. No response

Solution

1. Step 1: Check the condition for successful login

   The server checks if username is 'user' and password is 'pass' exactly.

2. Step 2: Evaluate given input against condition

   Input password is 'wrong', which does not match 'pass', so condition fails.

3. Final Answer:

   Fail with status 401 -> Option A

4. Quick Check:

   Wrong password = 401 Fail [OK]

Hint: Match exact username and password on server [OK]

Common Mistakes:

• Assuming any password works
• Confusing status codes
• Ignoring the else branch

4. This Astro server code is meant to authenticate users but has a bug:

export async function post({ request }) {
  const { username, password } = await request.json();
  if (username = 'admin' && password = '1234') {
    return new Response('Logged in', { status: 200 });
  }
  return new Response('Unauthorized', { status: 401 });
}

What is the bug and how to fix it?

medium

A. Use '===' instead of '=' in the if condition

B. Remove the await keyword

C. Use '==' instead of '=' in the if condition

D. Change Response to JSON response

Solution

1. Step 1: Identify incorrect operator in condition

   The code uses '=' which is assignment, not comparison, causing a bug.

2. Step 2: Use strict equality '===' for comparison in JavaScript

   Replace '=' with '===' to correctly compare values in the if condition.

3. Final Answer:

   Use '===' instead of '=' in the if condition -> Option A

4. Quick Check:

   Comparison needs '===' not '=' [OK]

Hint: Use '===' for comparison, '=' is assignment [OK]

Common Mistakes:

• Confusing assignment '=' with comparison '==' or '==='
• Removing await which is needed
• Changing response type unnecessarily

5. You want to protect a private Astro page so only logged-in users can see it. Which server-side approach is best to check authentication before rendering?

hard

A. Render the page fully and then ask for login

B. Check a JavaScript variable on the client to hide content

C. Use client-side localStorage to store login status

D. Check a session cookie on the server and redirect if missing

Solution

1. Step 1: Understand server-side protection needs

   Server must verify user identity before sending private content to prevent unauthorized access.

2. Step 2: Use session cookies for authentication

   Session cookies are sent with requests and can be checked on the server to confirm login status.

3. Final Answer:

   Check a session cookie on the server and redirect if missing -> Option D

4. Quick Check:

   Server checks session cookie before rendering [OK]

Hint: Always verify login on server before showing private pages [OK]

Common Mistakes:

• Relying on client-side checks only
• Using localStorage which can be manipulated
• Rendering private content before login check