You're reading from Building Production-Grade Web Applications with Supabase A comprehensive guide to database design, security, real-time data, storage, multi-tenancy, and more

Product type Paperback

Published in Aug 2024

Publisher Packt

ISBN-13 9781837630684

Length 534 pages

Edition 1st Edition

Languages

Typescript

Tools

Next.js

Concepts

Application Development

Author (1):

David Lorenz

View More author details

Table of Contents (20) Chapters

Preface

1. Part 1:Creating the Foundations of the Ticket System App

2. Chapter 1: Unveiling the Inner Workings of Supabase and Introducing the Book’s Project FREE CHAPTER

3. Chapter 2: Setting Up Supabase with Next.js

4. Chapter 3: Creating the Ticket Management Pages, Layout, and Components

5. Part 2: Adding Multi-Tenancy and Learning RLS

6. Chapter 4: Adding Authentication and Application Protection

7. Chapter 5: Crafting Multi-Tenancy through Database and App Design

8. Chapter 6: Enforcing Tenant Permissions with RLS and Handling Tenant Domains

9. Chapter 7: Adding Tenant-Based Signups, including Google Login

10. Part 3: Managing Tickets and Interactions

11. Chapter 8: Implementing Dynamic Ticket Management

12. Chapter 9: Creating a User List with RPCs and Setting Ticket Assignees

13. Chapter 10: Enhancing Interactivity with Realtime Comments

14. Chapter 11: Adding, Securing, and Serving File Uploads with Supabase Storage

15. Part 4: Diving Deeper into Security and Advanced Features

16. Chapter 12: Avoiding Unwanted Data Manipulation and Undisclosed Exposures

17. Chapter 13: Adding Supabase Superpowers and Reviewing Production Hardening Tips

18. Index

Why subscribe?

19. Other Books You May Enjoy

Adding password recovery

There are two things missing for a complete picture of authentication: the ability to register a new user account and the typical password recovery feature. Registration is covered in the next chapter, but we will look at the password recovery feature now.

Password recovery works in the exact same way as magic links, except for two differences:

After successfully clicking the Magic (Recovery) Link, you should forward the user to a page where the password can be changed (otherwise, it would be just the same as the magic link).
To be able to tell the different scenarios apart, we use type: "recovery" instead of type: "magiclink" for generating the token, though it’s effectively the same. For the built-in mailing system (which we don’t use), this ensures that a PASSWORD_RECOVERY event is fired when used on the frontend (onAuthStateChange), such that you could redirect to a page where the user can set the password...