Why authentication needs server-side logic in Astro - Quick Recap

Recall & Review

beginner

Why can't authentication be done only on the client side?

Because client-side code can be seen and changed by anyone, so it is not safe to trust it for checking who a user is.

beginner

What role does the server play in authentication?

The server checks the user's credentials securely and decides if the user is allowed access, keeping secrets safe from users.

intermediate

How does server-side logic protect user data during authentication?

It keeps passwords and tokens hidden on the server, so attackers cannot steal them by looking at the website code.

beginner

What is a common method servers use to remember authenticated users?

Servers often use secure cookies or tokens to remember who the user is after they log in.

intermediate

Why is it risky to trust only client-side authentication in Astro apps?

Because Astro apps generate static pages that users can inspect, so sensitive checks must happen on the server to stay safe.

What is the main reason authentication needs server-side logic?

A To make the website load faster

B To display user profiles

C To allow users to change their passwords on the client

D To keep user credentials secure and hidden

Server-side logic keeps sensitive data like passwords safe from users and attackers.

Which of these is NOT a secure way to handle authentication?

A Checking passwords only in client-side JavaScript

B Validating credentials on the server

C Using secure cookies to store session info

D Encrypting passwords on the server

Client-side only checks can be bypassed or changed by users, so they are not secure.

In Astro, where should authentication checks happen?

A Only in the browser

B On the server side

C In the static HTML files

D In CSS files

Astro apps should do authentication on the server to keep it secure.

What can happen if authentication is done only on the client side?

A Attackers can fake being logged in

B The website will load faster

C Users will have better experience

D Passwords will be stronger

Client-side only authentication can be tricked, letting attackers pretend to be someone else.

What is a secure way to remember a logged-in user?

A Storing user info in plain text on the client

B Saving passwords in local storage

C Using secure cookies or tokens set by the server

D Using only client-side variables

Secure cookies or tokens managed by the server keep user sessions safe.

Explain why authentication must involve server-side logic in Astro apps.

Think about what users can see and change in their browser.

Describe how server-side authentication improves security compared to client-side only.

Focus on what the server can do that the client cannot.

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