Bummer! This is just a preview. You need to be signed in with an account to view the entire instruction.


Restricting Access

Now that we have a basic registration and sign-in mechanism is place we need a way to determine which routes should require authentication and which shouldn't. For example, users should only have access to the "Entries" list page and the "Add Entry" page after they've signed-in into the web app. And if a user attempts to access either of those pages before they've authenticated, the web app...