Authenticate and test OAuth flow with Remix's RemixAuthAuthenticator for GitHub, check auth status, navigate callback URLs without login.

Set up GitHub OAuth2 flow, handle redirects, retrieve user data, and seamlessly integrate with RemixAuth for onboarding 

Implementing OAuth2 Flow with GitHub for User Authentication

[00:00] Let's first go to our login where we're going to be rendering the provider connection form. If you dive into that, it's a pretty simple form, just form here with the status button and shows an icon for the provider that we're connecting to. Not a whole lot of complex stuff going on here.

[00:18] Probably the most important part here is this form action, that the action goes to slash auth slash provider name, and we're going to provide GitHub. The action is going to be auth GitHub, which we will be doing some stuff to in a bit. Down here below our login form,

[00:35] we're going to render that provider connection form. The type is going to be login, and that's really just for the label that we show. It should say login with GitHub versus sign up with GitHub versus connect with GitHub. That's our type, and then the provider name. Right now, all we support is GitHub,

[00:54] but in the future, you definitely support others. If I log out here and then we go to login, then we have this login with GitHub. Now, this is going to post over to the action, which we don't have anything there yet. Let's go to our auth.GitHub.

[01:13] That's the action that we're posting to. You can even take a look at the DOM output here. We saw it in the component, but there it is. The action, that's the login button here, the login with GitHub, that action goes to slash auth slash GitHub. So that is this action right here. Okay, great. So we're going to need

[01:32] the authenticator that we made in the previous step, and we're going to use that to authenticate with GitHub. So we'll say the strategy we want to use is the one called GitHub. If we dive into where this is defined, we've got GitHub right there. So that is where that name is associated.

[01:50] Then we're going to pass it the request so that it can use cookies and all that stuff. So let's get the request from the data function args. Then, yeah, we're throwing a 500. We don't want to do that. We actually want to await this, and then we'll just return that value because it's either going to throw

[02:09] a redirect or it's going to return a redirect. Either way, I actually don't care that much. It's going to handle that action for us, depending on the current state of the user session and all of that stuff. Ultimately, that will send us over to GitHub,

[02:25] and then GitHub will send us back over here. So let's actually get that far at least. So if I click login with GitHub, then this will send me over to my demo app. So that's awesome. Let's go back and let's finish this up. Because once we confirm with GitHub, it's going to send us over here.

[02:43] So let's bring in the authenticator. Let's also bring the request in as data function args. We're going to do something very similar actually here. So we'll say this, except in this case, if there is a problem of some kind or if it's successful,

[03:03] we don't want the authenticator to send us over to the homepage or anything, because we're going to be managing the session and setting up the user's login and all of that stuff. So what we're going to say is throw on error and set that to true, and then we'll get our results here. So by saying throw on error,

[03:21] that communicates to RemixAuth, that we're going to be managing all this stuff. If there's some error or something, don't you try to send them to the error page or anything. We're going to handle that. Okay. So here's our results. I'll call that data, and then we'll console.log data. All right. So let's test this out. We'll go login with GitHub.

[03:39] That'll take us over here. You should note that it will only take you over here one time. After you've actually already authorized, then it will actually take you to GitHub, but GitHub will say, oh, they already authorized it, so I'll just send them back. So you actually will only see this page the one time. If you want to, you can go into

[03:58] your GitHub user settings and unauthorize it if you want to go through the whole flow again. Okay. So I'll authorize Kent C. Dodds, and I'm getting redirected, and you have successfully authenticated with GitHub. Not really though, JK. Because we haven't actually implemented all that stuff yet, but we'll get to it. Let's take a look at our logs.

[04:17] Here I've got my data. There's my user ID. Here's my e-mail, username, all of that stuff. So the whole flow actually did work. We're getting some warnings from MSW because that's how we have MSW configured to give us warnings if there are requests made without us mocking those out,

[04:35] which we'll take care of in the next step. But you'll notice we've got a post to the access token to get an access token, a get on the user to actually get the user's profile information as well as their e-mails, and all of that stuff ultimately to resolve to this profile information,

[04:53] which we can then use as part of our onboarding. We'll talk more about what we're going to do with this data there. But this is all the data that we need to get this user onboarded into our app. So just to review what we did in this step is, first, we added a form to

[05:10] our login page that says Provider Connection Form. It literally just renders a button, but it is an action that goes to this action in our routes auth GitHub action here. We're going to use the authenticator authenticate with GitHub.

[05:27] Because our request hasn't gone through the GitHub flow yet, it's going to say, okay, I need you to go over to GitHub first so that we can get all the data necessary for your authentication flow. So then we look at our callback right here,

[05:45] and we can see our data right there. Of course, we're calling authenticator authenticate. We say throw on error to say we're going to manage all of those things. I think one thing that might be useful for you to test out is to console log the request.url because there's

[06:03] some pieces on that URL that I think you will find pretty interesting. So if I say login with GitHub, then that's going to send me over to GitHub, but it sends me back so fast that you don't see it. That's what I was talking about where now it's not going to show us that anymore. But because I logged out that URL,

[06:21] here it is right here. So we get a code and we also get state. So the code is the access code or access token that allows us to start making requests. So we're going to swap that code for an actual access token, and then start making requests to the GitHub API acting as this user.

[06:41] So that is something that this is implementation detail stuff of RemixAuth, but that's what that code is for. The state is another thing that RemixAuth actually generates for us so that RemixAuth can associate the state for a particular user who's going through

[06:58] this flow to the access code or this code that they're given. So that's another thing that's implementation detail thing for RemixAuth. RemixAuth actually uses that session storage object that we gave to it to store some of this information,

[07:14] and that will become very relevant to us in the next step of this exercise. But once we hit that URL, then RemixAuth takes that code and that state, and it starts making those requests with GitHub's API to get all the data until ultimately we're able to retrieve all of our data.

[07:32] That is the OAuth2 flow using GitHub.

Testing the OAuth Flow with GitHub Authentication 

[00:00] So now we're going to test the actual auth flow. And so if you created a OAuth application in GitHub, you should actually be able to test the auth flow in this exercise once we're finished. So you're going to go to the auth GitHub callback route that Kelly put together for us and fill in a couple of things

[00:17] in there to authenticate using the RemixAuthenticator, the RemixAuthAuthenticator object that we just created. And then we're also going to go to the regular GitHub URL and use the authenticator there as well. So the flow is kind of like, here I'm on my login page.

[00:36] I click the button that takes me over to this page. That's going to see, am I already authenticated? Have I already given permission, all that stuff? If I haven't, then it's going to send me through the callback URL, or after it's finished doing that check, it's going to send me to the callback URL.

[00:53] And so that's the typical flow for OAuth 2 that we're going to be testing out in this one. We're not going to actually get to logging the user in quite yet, we've got more stuff to do, but you can go ahead and log the result of doing this authenticator process so that you can see that things are working

[01:12] the way that they should be. So have a good time with this one and we'll see you when you're finished.

Most web applications feature user accounts in one form or another.

To the user, having a login form seems simple enough. But behind the scenes, there's a lot going on. You need to securely store and manage user sessions, handle authentication and authorization, and protect against malicious attacks.

Without knowledge of the underlying concepts, it's easy to make mistakes (even if you decide to use a third party service or library to do all the hard work for you). Weak authentication systems, misconfigured route protection, and flawed session management all lead to vulnerabilities and negative user experiences.

The Authentication Strategies & Implementation workshop is your guide to implementing industry standard user account flows in a modern web application.

Securely managing passwords, enabling two-factor authentication, and integrating with third-party providers are just some of the processes you will practice. You'll also learn how to handle user preferences, session data, and send emails to users. This will take you all the way to the point where you could easily add Single-Sign On (SSO) support–a must if you’re building a business-to-business application.

There are a lot of moving parts to consider, but this workshop will give you the confidence to tackle them all.

## Cookies

The workshop begins by diving into cookies. This fundamental part of web browsing is often misunderstood, but important to understand. We keep it simple to ramp you up slowly on the web’s original state management solution. This also introduces us to important UI patterns you’ll want to use in other areas of web development as well. It’s surprisingly deep! Topics include:

- Storing user theme preferences in a cookie
- Server-side cookie handling
- Using fetchers for non-navigation mutations
- Optimistic UI updating to apply changes immediately

## Session Storage

Storing user preferences in cookies is fine, but you need to be more careful when it comes to session data. It's vital that users with devtools or malicious client-side JavaScript can't access or modify the data inside of cookies. In this section, you'll learn:

- Cookie-based session data persistence
- Properly getting, setting, and updating session data
- Deleting data after reading
- The flash pattern for short-lived messages

## User Sessions

Depending on the amount of data you need to store, it may make sense to use a different storage mechanism for session data. For this workshop we will continue to use cookies, however we will switch to using a dedicated session cookie. This section will teach you:

- Create a session storage object for storing user data
- Transform form submissions into user objects for storage
- Retrieving user information from cookies then the database

## Passwords

Passwords are the most common way to authenticate that a user is who they say they are. Obviously, storing them in plain text is a bad idea, but even encryption isn't enough. You need to properly prepare to securely handle passwords:

- Create a Password model in the database
- Generate secure password hashes with the battle-tested bcrypt algorithm
- Protection against password attacks
- Update signup route to securely create records

## Login & Logout

At this point, you have the ability to create users and store their passwords. But how do you actually log them in? And how do you log them out? In this one we’re also going to learn about imperative mutations which you’ll definitely want to know for other app features. This section will teach you:

- Verify a user's password hash with bcrypt
- Handling optional vs. required user data
- Guard against timing attacks
- Clearing session data on logout
- Handle edge cases like deleted accounts
- Set expiration dates for session cookies
- Implement automatic logout after a set idle time

## Protecting Routes & Role-Based Access

Most web application have routes that you need to be logged in to access. It's one thing to prevent this in the UI, but the real thing you need to do is protect the data that powers those pages. There are also considerations for different user roles and permissions. This section will teach you how to:

- Ensure users only access data they own
- Restrict private pages to logged in users
- Implement smart redirects for login and logout
- Specify and enforce permissions with Role-Based Access Control (RBAC)

## Managed Sessions

Imagine a user logging in on a public computer, who then forgets to log out. This security risk can be mitigated by implementing a session management feature:

- Add a session model to the database
- Update auth utils, login, and logout routes to query sessions
- Refactor for session expiration support
- Create a page for displaying & managing active sessions

## Email Verification & Password Resets

Email is one of the most common ways to verify a user's identity. If a user loses access to their account, needs to reset their password, or wants to change their email address, you'll need to send them an email. While the actual sending of the email is best handled by a third-party service, the process flow behind the scenes is what you'll need to implement:

- Integrate a third-party email API
- Share session data between routes for multi-step flows
- Style HTML emails
- Generate time-based one time passwords (TOTP) for password resets
- Force verification of email address change

## Two-Factor Authentication

Two-factor authentication (2FA) is a great way to add an extra layer of security to your application. It requires the user to enter a code from a second device along with their username and password. Even if an attacker determines a password, they won't be able to access the account without the second factor. In this section, you'll add 2FA to the Epic Notes application:

- Handle the 2FA enable flow
- Provide the user with a QR code
- Implement a 2FA code input form
- Verify the code and log the user in
- Require re-verification
- Provide option to disable 2FA

## Third-Party Authentication

There are several reasons to use third-party authentication providers. It can be a great way to reduce friction for users, or allow easier access to other data. The most common way to do this is with OAuth 2. Once you’re finished with this section, you’ll be geared up to implement third party auth with any provider. Including Single-Sign On (SSO) flows. We’ll be following these steps:

- Add an authentication strategy to enable GitHub login
- Create a connections model to associate users with providers
- Prevent duplicate account connections & hijack attempts
- Pre-fill user account data based on third-party login
- Mocking third party APIs for testing
- Gracefully handle login errors
- Implement smart redirection to return to original page after login

Learn best practices for managing user sessions, passwords, 2FA, email verification, OAuth, and more in the Authentication Strategies & Implementation Workshop!

Authentication Strategies & Implementation

Kent C. Dodds

Full Stack Vol 1

Discover the ins and outs of web authentication, including role-based access control, session management, third-party authentication, 2fa, and more.

Intro to Authentication Strategies & Implementation Workshop

Intro to Authentication Strategies & Implementation

Intro to Cookies

Learn how to properly set and manage the theme preference in a form using Conform and UseFetcher. 

Implement a theme switcher with hidden input, user-based theme, and no page refresh using useFetcher.

Creating a Theme Switcher with Form Submission and Fetcher in React

Implementing Theme Switching with Conform and UseFetcher

Wire cookie-based dark mode preference into app using root TSX file and theme module for seamless light-dark theme toggling.

Master cookie-based theme selection, updating UI dynamically for a superior user experience in your web app.

Implementing Cookies for Theme Selection

Adding User Preference for Dark Mode

Optimize UI for theme switching: Instantly update UI on theme switch, improving user experience by eliminating network delay.






Leverage useTheme hook for optimistic theme changes: Extract data from fetchers, manage fallbacks, and simplify with Remix for seamless UI updates.






Implementing Optimistic UI with Remix

Implementing Optimistic UI for Theme Switching

Discover the value of taking breaks to refresh and solidify information in your brain during your learning journey. Don't underestimate the power of a short break to enhance your learning experience.

Dad Joke Break Cookies

Cookies

Intro to Session Storage

Utilize cookies for dynamic toast messages in your web app: Set and read cookie values to display informative alerts and success notifications to users.






Set up secure cookie session storage for toast messages in server-side code: Configure, sign, and rotate with step-by-step guidance.










Configuring Cookie Session Storage for Toast Messages

Toast Messages with Cookies

Implement Toast messages for user feedback during delete actions: Set up frontend and backend components for seamless notification display.

Utilize cookie sessions for dynamic toast messages: Read, set cookies, serialize objects, and manage toasts via session storage, independent of global state.

Managing Toast Messages with Cookie Sessions

Adding Toast Notifications to Delete Functionality 

Efficiently delete notes, set multiple cookies using utility, eliminate persistent toast for a smoother user experience.






Sync browser-server state efficiently: Unset and serialize cookie properties, optimize performance, and enhance user experience with header management insights.

Efficiently Updating and Serializing Cookies 

Improving Note Deletion Functionality with Multiple Cookies

Use "flash and get" for temp notifications like toasts, skip needless unsets, and embrace session management's flashes.

Use Flash API to auto-remove toast messages on the next get call, maintaining clean code and up-to-date cookie storage.






Efficiently Removing Toast Messages with Flash API

Implementing Flash Messages for Temporary Notifications

Dad Joke Break Session Storage

Session Storage

Intro to User Sessions

Securely manage user login info with separate session cookies, similar to Toast messages in session storage. Gain valuable insights for effective handling.

Set up secure session storage for user info in cookies with RemixRunNode. Configure for enhanced security and protection against unauthorized access.

Secure Cookie Session Storage 

Managing User Sessions with Separate Cookies

Learn how to authenticate users, set session values, and create cookies for user identification and access control.

Learn how to create a secure login process using form data, user validation, and session storage, including error handling and user authentication.

User Authentication and Session Management with Login Forms

User Authentication and Session Management

Resolve user IDs to display avatars for a personalized logged-in experience. Refresh the page to see avatars appear dynamically.

Implement user auth and session management with Prisma, TypeScript, and session storage, including retrieving user data from cookies for UI integration.

Handling User Authentication and Session Management with Prisma

Load User Avatars

Dad Joke Break User Sessions

User Sessions

Intro to Password

Learn how to add a one-to-one password model in Prisma schema with optional fields, understanding the unique constraints and implications for database design.

Learn how to create one-to-one relationships in Prisma database schema and handle password security by separating password hash in a separate model.

Model Relationships and Handling Passwords in Database Schema

Creating an Optional Password Model in Prisma Schema

Update seed script to generate secure passwords for user accounts, ensuring all users have passwords and enhancing app security.

Utilize bcrypt to generate secure password hashes, integrate them into seed scripts, and bolster your test suite.

Secure Password Creation with Prisma

Generating Passwords for Secure User Creation

Learn how to integrate password creation functionality into an existing user creation process, allowing for a seamless onboarding experience.

Securely create and hash passwords during user sign-up with bcrypt.js for data integrity and improved Node.js app performance.

Creating and Hashing Passwords for User Sign-Up

Enhancing User Creation by Adding Passwords

Dad Joke Break Password

Password

Verify passwords with bcrypt, UI for authenticated users, and hooks to prevent timing attacks. 

Intro to Login

Learn how to compare hashed passwords for secure authentication using bcrypt compare in a Node.js application.

Learn how to securely verify passwords during the user login process, ensuring that the password hash matches and avoiding potential security risks. 

Implementing Secure Password Verification in User Login

Secure Password Authentication with bcrypt Compare in Node.js

Create utility functions to selectively hide new note, delete, and edit buttons on user profiles to ensure they are only visible on the user's own profile.

Learn how to use utility functions to handle user data and create dynamic UI elements based on authentication status and user roles. 

Leveraging Utility Functions for User Data Handling and UI Customization

Securing UI Elements

Dad Joke Break Login

Login

Make logout button functional, auto-logout after time, explore 'expires' cookie property, handle deleted user accounts.

Intro to Logout

Enhance web app security by converting logout link to a secure POST request instead of GET.

Implement secure logout with session storage, protect against CSRF attacks, post logout request, destroy session cookie, ensure user experience.

Logout Functionality with Session Storage and CSRF Protection

Transforming a Logout Link into a Secure Logout Form

Set session cookie expiration with 'Remember Me' checkbox, configure/update expiration for flexible session persistence without compromising security.

Configure session expiration with 'Remember Me' checkbox, enable users to stay logged in, and refresh cookie expiration for active sessions.

Implementing Remember Me Functionality

Implementing Remember Me Functionality for Login Sessions

Discover techniques to detect and destroy invalid sessions, preventing unnecessary database requests.

Learn how to handle sessions without user IDs, destroy sessions, and handle weird states to ensure proper functioning of your web application.

Destroying Sessions and Handling Weird States

Managing Inactive User Sessions

Create an inactivity logout modal for web apps, explore use cases, detection methods, and customization for a seamless experience.

Auto-logout users after inactivity in a web app. Set up logout timer, detect user activity, use imperative submissions for efficient session control.

Auto-Logout Functionality

Implementing Automatic Logout with Modals

Step away and engage in physical activity to recharge your brain and enhance your learning experience. Return revitalized and ready to absorb more knowledge.

Dad Joke Break Logout

Logout

Secure routes with access control, authenticate, authorize users, and enforce data restrictions for app safety.

Intro to Protecting Routes

Create protected routes to restrict logged-in users and auto-redirect them to the homepage.

Centralize auth logic, use requireAnonymous function for login/signup routes, ensure proper redirection.

Creating an Auth Utility 

Creating Protected Routes 

Craft dynamic profile page: edit details, change pic, download data, delete, auth, error handling.

Protect routes/actions with requireUserId to limit access to authenticated users, ensuring data security.

User Authentication and Authorization

Building a Profile Page 

Authenticate and authorize users for secure note access and actions, enforcing ownership verification.

Secure your app with user auth and authorization. Protect routes, handle user IDs, enhance security.

Authorization and User Authentication

Securing User Access 

Improve UX with post-auth redirection, taking users back to their original location for efficiency.

Secure user auth redirects with optional URLs to protect sensitive info.

Handling Redirects Safely in User Authentication

Redirect Functionality 

Take a moment to enjoy a dad joke, take a break, and come back recharged for the remaining content. Refreshments and high fives optional!

Dad Joke Break Protecting Routes

Protecting Routes

RBAC simplifies permissions, secures actions, enables granular control, attaches permissions to roles, and enhances app security and scalability. 

Intro to Permissions

Establish role-based access control with Prisma's many-to-many relationships for users, roles, and permissions.

Design Prisma models for permissions, roles, and data integrity with many-to-many relationships.

Modeling Permissions and Roles in Prisma Database

Role-Based Access Control with Prisma

Seed roles and permissions, assign to new users, optimize seeding for local and production environments.

Update seed script: delete, create, connect roles, permissions, and generate permissions dynamically for cleaner code. 

Seed Data

Managing Roles and Permissions

Implement user permissions, distinguish admin from regular users, handle user-specific actions, and automate permission checks for robust app development.

Implement role-based permissions for note deletion, hide unauthorized delete options for a seamless user experience.

Implementing Role-Based Permissions

Implementing User Permissions and Authorization Logic

Implement user permissions to secure admin pages and optimize queries with utility functions and loaders.

Implement role-based access control, create permission checks, secure backend actions, and manage UI permissions for app security.

Implementing Role-based Access Control and Permissions

Securing Admin Pages with User Permissions

Breaks enhance learning, prevent brain overload, and improve retention. Incorporate them for a better study experience.

Dad Joke Break Permissions

Permissions

Implement simultaneous sign-out across sessions with managed sessions and database updates for proactive session deletion.

Intro to Managed Sessions

Store user session data in the database, update download feature, and explore seeding session limitations.

Create session model, manage expiration, relate to user ID, and enhance login process for efficient, secure DB  

Integrating User Sessions into the Login Process

Managing User Sessions and Allowing Data Downloads

Move from user ID to session-based auth, update AuthServer to resolve session IDs to user IDs for login/signup.

Enhance authentication with session IDs, rename variables, manage sessions for login/signup, and handle session deletion with error resilience.

Authentication Logic with Session IDs and User Creation

Implementing Session-Based Authentication

Switch to session-based auth, update routes, auth server, and rename user ID to session ID for security

Refactor login/signup to use session-based auth, update variables, queries, and validate sessions for security, performance. 

Updating Login and Signup Routes to Use Sessions instead of User IDs

Improving Login and Signup Flows with Session Management

Learn how to implement a button that allows users to delete multiple sessions, ensuring proactive logout and improved security.

 Explore techniques for session deletion and session ID verification to enhance user control and privacy.

Managing Sessions and Sign Out in Web Applications

Proactive Session Management

Take a well-deserved break, engage in activities you enjoy, like playing video games or reading a book, before diving back into the course content with renewed energy.

Dad Joke Break Man Sessions

Managed Sessions

Mock email sending in development, use Resend for production, leverage React Email components, and pass data for efficient email workflow.

Intro to Email

Set up email API keys, manage environment variables, create send email function, and use mocks for dev.   

Configure env variable, set up email server, make fetch calls with Resend API, handle errors, mock for local dev.

Sending Emails with the Resend API using Fetch

Integrating Email Services 

Use MSW to create mock API handlers for development and testing, saving costs and improving performance.

Setting Up a Mock Server with MSW Node

Mocking APIs with MSW and Testing

Integrate email verification in sign-up, log email content for testing, enhance onboarding process. 

Implement email verification with custom content, utility functions, user ownership check, and onboarding redirection.

User Verification Emails

Email Verification Flow

Safely pass user emails between signup and onboarding using cookies for verification and security. 

Safely pass data between routes with session storage and cookies for seamless web app data persistence.

Passing Data Between Routes

Secure Email Transfer and Storage with Cookies for Onboarding

Discover the importance of taking regular breaks to optimize brain function and overall well-being. Learn how simple physical activity can boost blood flow and enhance productivity in your coding journey.

Dad Joke Break Email

Email

Implement secure email ownership verification with time-based OTPs, rate limiting, and use cases for 2FA and account recovery.

Intro to Verification

Learn how to create a database model for storing verification information and generate one-time password data for secure authentication processes.

Build Prisma verification model for secure OTPs, expiration, unique constraints, target/type lookup, robust verification.

Authentication Strategies & Implementation

Authentication Strategies & Implementation

Transcript

Testing the OAuth Flow with GitHub Authentication

Transcript