Role-based access control in Remix - Interactive Code Practice

Practice - 5 Tasks

1fill in blank

easy

Complete the code to check if the user has the 'admin' role.

Remix

if (user.roles.includes([1])) {
  // allow access
}

Drag options to blanks, or click blank then click option'

A'user'

B'admin'

C'guest'

D'editor'

Attempts:

3 left

💡 Hint

Common Mistakes

Using a role name that does not exist in the user's roles array.

Forgetting to use quotes around the role name.

The 'includes' method checks if the 'roles' array contains the string 'admin'. This is how you verify if the user has admin access.

2fill in blank

medium

Complete the code to restrict access to users with the 'editor' role.

Remix

export function loader({ request }) {
  const user = getUserFromRequest(request);
  if (!user.roles.includes([1])) {
    throw new Response('Forbidden', { status: 403 });
  }
  return json({ data: 'Editor content' });
}

Drag options to blanks, or click blank then click option'

A'editor'

B'admin'

C'guest'

D'user'

Attempts:

3 left

💡 Hint

Common Mistakes

Using the wrong role name for the check.

Not throwing a response to block unauthorized users.

This code checks if the user has the 'editor' role. If not, it throws a 403 Forbidden response to block access.

3fill in blank

hard

Fix the error in the role check to correctly verify if the user has 'guest' role.

Remix

if (user.roles.[1]('guest')) {
  // allow limited access
}

Drag options to blanks, or click blank then click option'

AindexOf

Bfind

Cincludes

Dfilter

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'find' which returns the element or undefined, not a boolean.

Using 'filter' which returns an array, not a boolean.

The 'includes' method returns true if the array contains the specified element. Other methods do not return a boolean directly.

4fill in blank

hard

Fill both blanks to create a role check that allows access only if the user has 'admin' or 'editor' role.

Remix

if (user.roles.includes([1]) || user.roles.includes([2])) {
  // allow access
}

Drag options to blanks, or click blank then click option'

A'admin'

B'user'

C'editor'

D'guest'

Attempts:

3 left

💡 Hint

Common Mistakes

Using roles that do not grant access.

Forgetting to use the logical OR operator.

This condition checks if the user has either 'admin' or 'editor' role to allow access.

5fill in blank

hard

Fill all three blanks to create a function that returns true if the user has any role in the allowedRoles array.

Remix

function hasAccess(user, allowedRoles) {
  return user.roles.some(role => role === [1] || role === [2] || role === [3]);
}

Drag options to blanks, or click blank then click option'

AallowedRoles[0]

BallowedRoles[1]

CallowedRoles[2]

Duser.roles[0]

Attempts:

3 left

💡 Hint

Common Mistakes

Comparing user roles to wrong variables.

Not using the 'some' method correctly.

This function checks if any role in the user's roles matches any of the first three roles in allowedRoles. Using 'some' returns true if any match is found.

Practice

1. What is the main purpose of role-based access control (RBAC) in a Remix app?

easy

A. To store user passwords securely

B. To speed up page loading times

C. To style components differently for each user

D. To limit user actions based on their assigned roles

Solution

1. Step 1: Understand RBAC concept

   RBAC means users get permissions based on their roles, like admin or guest.

2. Step 2: Identify RBAC purpose in Remix

   In Remix, RBAC controls what pages or data a user can access depending on their role.

3. Final Answer:

   To limit user actions based on their assigned roles -> Option D

4. Quick Check:

   RBAC = limit actions by role [OK]

Hint: RBAC controls what users can do by their roles [OK]

Common Mistakes:

• Confusing RBAC with performance optimization
• Thinking RBAC is for styling UI
• Mixing RBAC with password security

2. Which code snippet correctly checks a user's role in a Remix loader function?

easy

A. const user = await getUser(request); if (user.role !== 'admin') throw new Response('Forbidden', { status: 403 });

B. const user = getUser(request); if (user.role == 'admin') return redirect('/admin');

C. const user = await getUser(request); if (user.role = 'admin') return null;

D. const user = await getUser(request); if (user.role !== 'admin') return 'Access granted';

Solution

1. Step 1: Identify async user fetching

   Using await with getUser(request) is correct to get user info asynchronously.

2. Step 2: Check role comparison and response

   const user = await getUser(request); if (user.role !== 'admin') throw new Response('Forbidden', { status: 403 }); correctly compares role with !== and throws 403 response if not admin.

3. Final Answer:

   const user = await getUser(request); if (user.role !== 'admin') throw new Response('Forbidden', { status: 403 }); -> Option A

4. Quick Check:

   Async fetch + role check + 403 response = const user = await getUser(request); if (user.role !== 'admin') throw new Response('Forbidden', { status: 403 }); [OK]

Hint: Use await and strict role check with Response for access control [OK]

Common Mistakes:

• Forgetting await when calling async functions
• Using assignment (=) instead of comparison (== or !==)
• Returning wrong responses on unauthorized access

3. Given this Remix loader code, what happens if a user with role 'user' tries to access the page?

export async function loader({ request }) {
  const user = await getUser(request);
  if (user.role !== 'admin') {
    return redirect('/login');
  }
  return json({ message: 'Welcome Admin' });
}

medium

A. The loader returns null and page is blank

B. The user is redirected to '/login' page

C. The page throws a 403 Forbidden error

D. The user sees 'Welcome Admin' message

Solution

1. Step 1: Analyze role check condition

   The code redirects if user.role is not 'admin'. A 'user' role is not 'admin'.

2. Step 2: Determine loader behavior for 'user' role

   Since role is 'user', the redirect('/login') runs, sending user to login page.

3. Final Answer:

   The user is redirected to '/login' page -> Option B

4. Quick Check:

   Non-admin role triggers redirect [OK]

Hint: Non-admin roles trigger redirect to login [OK]

Common Mistakes:

• Thinking user sees admin message
• Assuming 403 error instead of redirect
• Ignoring redirect and expecting blank page

4. Identify the error in this Remix loader code for role-based access control:

export async function loader({ request }) {
  const user = getUser(request);
  if (user.role !== 'admin') {
    throw new Response('Unauthorized', { status: 401 });
  }
  return json({ data: 'Secret Data' });
}

medium

A. Missing await before getUser causing user to be a Promise

B. Incorrect status code; should be 403 instead of 401

C. Throwing Response is not allowed in loader functions

D. json() function is not imported from Remix

Solution

1. Step 1: Check async function usage

   getUser is likely async, so missing await means user is a Promise, not user data.

2. Step 2: Understand impact of missing await

   Without await, user.role is undefined, causing runtime error or wrong behavior.

3. Final Answer:

   Missing await before getUser causing user to be a Promise -> Option A

4. Quick Check:

   Async call missing await = Missing await before getUser causing user to be a Promise [OK]

Hint: Always await async calls before accessing properties [OK]

Common Mistakes:

• Ignoring missing await and expecting user object
• Confusing 401 and 403 status codes
• Thinking throwing Response is invalid in loader

5. You want to restrict a Remix route so only users with roles 'admin' or 'manager' can access it. Which loader code correctly implements this with a redirect for others?

export async function loader({ request }) {
  const user = await getUser(request);
  // Fill in the role check
}

hard

A. if (user.role === 'admin' || user.role === 'manager') return redirect('/not-authorized');

B. if (user.role !== 'admin' || user.role !== 'manager') return redirect('/not-authorized');

C. if (user.role !== 'admin' && user.role !== 'manager') return redirect('/not-authorized');

D. if (user.role === 'admin' && user.role === 'manager') return redirect('/not-authorized');

Solution

1. Step 1: Understand role conditions for access

   Users allowed are 'admin' or 'manager', so others must be redirected.

2. Step 2: Choose correct logical operator

   Use AND (&&) with !== to check if user is neither 'admin' nor 'manager'.

3. Step 3: Verify redirect logic

   If user role is not admin and not manager, redirect to '/not-authorized'.

4. Final Answer:

   if (user.role !== 'admin' && user.role !== 'manager') return redirect('/not-authorized'); -> Option C

5. Quick Check:

   Redirect if not admin AND not manager = if (user.role !== 'admin' && user.role !== 'manager') return redirect('/not-authorized'); [OK]

Hint: Use && with !== to exclude multiple roles [OK]

Common Mistakes:

• Using || instead of && causing wrong redirects
• Checking for both roles with && equality (impossible)
• Redirecting allowed roles instead of others