How to Set Up Protected Routes in Your React Application
Require authentication for users to access your page
Often times, when you’re building a web application, there’s some kind of routing involved with authentication. You want to restrict user access to certain pages or you have your whole application behind a login screen.
React router is a great way to go by routing, but you don’t really have the option to protect routes from being accessed by anyone. Luckily the solution to this is really simple and straightforward.
In this tutorial, I would like to show you what was my solution to the problem and how I got around it. I’ll start from scratch using create-react-app and only include the absolute necessary things so you can follow along. Without further ado, let’s jump into coding.
Modifying the index file
We will achieve protection by creating a custom component that will handle incoming requests. We have the plain old
Route component in React. This will be used for the sole public route we have: the login page. We also want to have a custom component as well that will handle private routes, let’s call it
The purpose of the component will be very simple: If the user has been authenticated, render the passed component. Otherwise, redirect them to the login page.
As you can see, I’ve imported
react-router-dom. I also created some components so we can test out routing.
ProtectedRoute will work the following way:
- It expects a
componentprop, the one it should render
- It also expects a path so it knows what component to render on which URL
Here I defined the
Dashboard component two times. This is because we want to land on the Dashboard if no path has been defined. This is what line:15 handles. We also want to load in the Dashboard if the user types in an invalid URL. By omitting the
path attribute on line:17, we tell React Router to fallback to the provided component.
So let’s see how the
ProtectedRoute component works on the inside.
Creating private routes
So what’s inside the custom component we’ve imported? It’s actually really simple, we only have a render function:
We get the component from the props and return it if the user has been authenticated. I’ve also made use of
isAuthenticated turns out to be false, we redirect the user to the login page.
So how do we actually decide if the user is authenticated or not? What should we assign to
localStorage or a combination of both or maybe something else. Either way, we want to store some information about the user on the client side so we know when they are logged in.
To prevent forgery, this information may be the presence or absence of a token that you also verify on you server side. This way, you make sure that users cannot log in based on only the presence of the
token key. It ensures that it is its value that actually matters.
As you see from the gif above, if I refresh the page, it takes me to the login screen. If I try to access any other route that has restrictions, I get redirected back to the login page. If I set a token — no matter the value for now — I can access those pages. Also note that if I try to access a route that doesn’t exist while I’m logged in, I land on the Dashboard. As soon as I clear the storage, I lose my access.
To summarise: Even though your React code base will be obfuscated, the way your client application works can be reverse engineered. This is why it is essential that everything that involves authentication or authorization should be backed up by a server side implementation.
Thank you for taking the time to read through, let me know your thoughts on this approach in the comments below. What would be your security solution? 🔒