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

[00:00] This is our note ID route. So let's go in there. We're going to start in our loader to determine whether or not we should display these. Right now, Kali's got us displaying these all the time, saying that we can delete is true, but that is not the case. So let's come up here and let's first get the user ID.

[00:18] So user ID is await, get user ID from our server utils, request here, request there. There we go. So now we've got the user ID and we can use that to determine whether the user has permission.

[00:34] So we'll come down here and we'll say permission is equal to now, remember like unauthenticated users can look at this page as well. So if they're unauthenticated, we don't even need to bother looking at the permission table. So we're going to conditionally do this. If the user ID is defined, then we'll do something.

[00:52] Otherwise we'll say the permission is null. So the thing that we're going to do is await, charisma permission find first. And we're going to have this query. First, let's add a select of ID of true. That way we aren't pulling more things from the database than we need. We only need to know whether the permission exists.

[01:13] And so pulling the ID is just fine. Now our where clause is going to be a little bit tricky. So we're looking for a permission where the roles include the user. So the permission is connected to a user via the roles. And so we're going to select on the roles to make sure or to find all the permissions

[01:33] that the user has through their roles. So we're going to say where the permission has an associated role, where some of those roles have a user or have one of their users. So some of the users have an ID that match the user ID and that's going to be users.

[01:53] There we go. Hopefully that piece makes sense. I know it's a lot, but we need permissions where some of their roles have some users who have the ID of our user ID. So that is that piece of the where clause. But we also need to say that the entity is note.

[02:13] So that's the thing we're trying to determine their permission for. And the action that we want to determine is delete. That's the thing that we're checking for right now. And the access is going to actually depend on whether the note ID's owner matches the user ID.

[02:33] So the access is going to depend on the note.owner ID being equal to the user ID. If those two things are equal, then I'm looking at my own note and I need to know whether I have my permission to delete my own notes. If the user IDs do not match, then I need to have permission to delete any note.

[02:53] And that is, yeah, that is that query. And so then we can determine whether we can delete based on whether there's a permission for deleting. And that will get my UI up to date.

[03:10] So if I come down here and actually before I save this, let's pull this up in an incognito tab. And we can see that. We can delete, we can see that bar. So that's of course not what we want here. So we'll come down here to our UI now that we're passing that can delete and we can say data.candelete.

[03:29] If I save that, Cody can still see it because Cody is an admin, has proper permissions, but other users won't be able to see it anymore. So, so far so good. That's great. So now, even if you can't see it, you also need to verify in the action when the action is performed, because again, that's an endpoint

[03:48] that people can hit directly. And so we need to grab the owner ID and we can say, we could either put it right here, ID true or do owner ID. Honestly, I can't remember which one I did in the solution. So it doesn't really matter that much clearly.

[04:08] And since admins can delete notes, we don't want to filter by the user ID anymore. And so we'll remove that piece of this because we need to get the note whether or not the currently logged in user is the owner. Okay, so now that we've got the note, we're gonna do a permissions check again. That right there is telling me, huh, maybe we've got an abstraction here.

[04:28] Yeah, we'll work on that next. But here we've got our user.id. And actually in this case, we're requiring a user anyway. So there's no conditional logic here. This is just gonna be literally do that query because we definitely are going to have the user ID.

[04:46] And we'll say user.id right here and user.id. Everything else is the same as before. And now if we say, if there's no permission in this case, then they definitely shouldn't be able to do this at all. So we're gonna throw JSON and the JSON we're gonna throw has an error,

[05:05] a status of error. Actually, you know what? Because we're throwing, we're actually going straight to the catch boundary anyway. And so I don't need to do the status error or whatever, like clearly we're in an error. So all I need to do is I'll specify an error is unauthorized. We can say a message just to give people more context

[05:25] if somebody's integrating with this, I don't know. Just give them a little bit more context I think is reasonable. You don't have permission to delete this note. You need delete note, whatever, however you wanna do that. And then we'll add a status. This is the important part of 403. And actually, you know what?

[05:44] With that, let's come down here, right here and we'll add a 403 handler. And this, yeah, you don't have permission. You don't have permission, dot. And yeah, that should be enough. Like feel free to expound on that if you so desire. And now we also wanna get rid of this invariant response

[06:06] right here as well, because now even if the username doesn't match, it is possible that users or the user can delete the note. So we do the permission check more properly with role-based access control here. Okay, let's try this now. If I delete it, it does successfully go away.

[06:25] And yeah, we shouldn't even be able to see it if we don't have permission. But let's actually test that out really quick coming down here to the can delete. And we'll just do this true. Come over here. And yeah, that doesn't exist anymore.

[06:44] But if I try to delete this, I'm not even logged in. Oh, I'm gonna go to login. So here, I wanna show you this. And so we're gonna log in as this user, log in as that user, there we go. And then if we go to this user and try to delete this note, then you do not have permission.

[07:04] Ta-da! So we're in a good place. And of course, yeah, we don't even wanna show things that the user can't do because it's about user experience. So yeah, this user should not be able to do that. And yeah, we can delete notes now, hooray! So let's quickly review the stuff that we did in here to make this work.

[07:22] So first off, we need to get the user ID. We're using get user ID instead of require user ID because any user can look at this page. That's a public read as kind of a default for this page. So we get the user ID,

[07:39] and then we check for the user's permission if that user ID exists. So if there's a user that's logged in, then we're gonna check and see whether they have permission. The roles is probably the most complicated part. So we're looking for their permission where that permission has some roles, where some of those roles have some users,

[07:58] where some of those users have this ID of the user ID. So that filters down to whether a permission exists. Also, that has this entity of note, an action of delete, and access of own if I'm looking at my own note or any if I'm not.

[08:18] And that allows us to determine whether or not we're allowed to delete. And if we are allowed to delete, then we are able to display the bar. And then in our action, we require the user, because you can't do anything if you're not logged in. And then right here,

[08:36] we're gonna look for the permission in the same way. And if there's not a permission, then we'll return unauthorized. And we have added a unauthorized status handler for this so that users get at least some sense of some useful information there. And that is that.

[08:55] Now, I'll mention a couple of things. You could definitely apply this permission stuff to edit as well. So if the user has update capability, then we wanna show the pencil. If they don't, then let's not show the pencil. And so we're gonna have different permissions

[09:14] based on the different actions that the user can perform. In fact, you could expand this to say, instead of find first, you could say find many, and then say where the action is either delete or update. So you could do something like that and then use that to determine whether or not we display the bar as whether they can delete

[09:36] or they can edit as an example. So that is one thing. Another thing that we could do is probably, now that all we are using this user for is for the user ID, we could probably say require user ID rather than require user. So a couple of options that you have here to expand if you wanna go a little deeper,

[09:55] but that's as deep as we're gonna go. We're just adding permissions for the delete. And then in the next step, we're going to add some utilities because I'm looking at this and I'm thinking, I do not wanna have to do that all over my code base. Yeah, no thanks. So we're gonna make this better. So yeah, go ahead. And if you want to,

[10:14] Kelly's going to actually be making those utilities for us. Feel free to make those utilities yourself if you've got some time and you wanna give it a whirl. But it's all just like do JavaScript stuff. In the next step, we're actually going to use those utilities. So have a good time with that and we'll see you in the next step.

Implementing User Permissions and Authorization Logic

[00:00] So as Cody is an admin user, Cody should be able to delete other people's notes. So I should be able to hit this and get it deleted. Right now, that's not possible because we need to add some logic in our application to check the user's permissions and then check whether they're authorized to do this. And Cody should be authorized to do this.

[00:18] Kelly added a little bit of logic to make it so that it's easier to display this bar when we have those permissions. So you're going to be adding a little bit of logic to the loader for this page to determine whether the user should be able to see these or this bar. And then you're also going to add some logic to the action

[00:36] to verify that the user has authorization to perform this action. And so now it's not just whether this note belongs to this user. It's actually whether the user who's performing the action has permission to do that. So adding permissions to an app does definitely complicate a number of things.

[00:55] You have to do some manual checks on. And it would be cool if there was a Prisma extension that allowed us to do this automatically. And that certainly is a thing that somebody could build. Let me know if you do. But yeah, for now, we have to manually add some logic

[01:14] to verify that the user has permission to do what they're about to do. So that's what you're going to be doing in this exercise. I want to be able to delete this note if I am an admin user. Just make sure that I also can delete it if I have the permission to delete my own notes and it's my own note. So you've got a couple of things to do here.

[01:33] Have a good time.

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 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.

Creating a Verification Model in Prisma for User Verification

Implementing One-Time Password Verification with Database Storage

Implement a user verification workflow by generating URLs with pre-filled parameters, such as target, redirect, and creating database verification entries.

Learn how to generate secure one-time passwords for user verification in a signup flow. 

Authentication Strategies & Implementation

Authentication Strategies & Implementation

Transcript

Implementing User Permissions and Authorization Logic

Transcript