When a user requests a magic link for authentication in Supabase, what happens immediately after the request is made?
Think about security and temporary access.
Supabase sends a magic link email that expires quickly and can be used only once to ensure secure login.
Which Supabase configuration setting controls how long a magic link remains valid before expiring?
Look for a setting related to email confirmation expiry.
The correct setting is auth.email.confirmation_expiry, which defines the magic link expiry time.
Which practice best prevents replay attacks when using magic link authentication in Supabase?
Think about what happens after the link is used once.
Invalidating the magic link after first use stops attackers from reusing the link.
What is the correct order of steps in the magic link authentication process in Supabase?
Think about the natural sequence from request to login.
The user first requests the link, then receives it, clicks it, and finally is logged in after verification.
What is the best way to handle a user clicking an expired magic link in a Supabase application?
Consider user experience and security.
Informing the user and allowing them to request a new link balances security and usability.