Add email auth as an option for login

[0xAstraea]

Email Authentication Flow with Zupass Integration

Overview

This PR introduces a new email-based authentication flow using Zupass's Proof of Data (POD) system, complementing our existing ticket-based authentication. This enhancement provides users with a more flexible way to authenticate while maintaining high security standards through cryptographic proofs.

Authentication Flow

1. Initial SSO Validation

   • User arrives with SSO parameters (sso, sig, return_sso_url)
   • System validates SSO signature and payload
   • Parameters are stored for the authentication process

2. Email Proof Collection

   • User clicks "Sign In" button
   • System connects to Zupass client
   • Requests email proof with specific requirements:
     • Email address
     • Semaphore V4 public key
     • POD type verification

3. Proof Verification

   • Backend validates the proof structure
   • Confirms POD type is "zupass.email"
   • Verifies signer public key
   • Generates new SSO payload and signature

4. Session Completion

   • System creates authenticated session
   • Redirects user back to Agora with new SSO parameters
   • Maintains compatibility with existing Discourse SSO

Testing Instructions

1. Start the development server:

yarn run dev

2. Access the auth page with SSO parameters
3. Test both email and ticket authentication flows
4. Verify successful redirection to Agora
5. Confirm session persistence

Future Improvements

As noted in the code comments:

• Potential to emit PODs of received PCDs
• Remove the need for separate email and ticket flows
• Clean up unused components and improve type safety

[vercel]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name	Status	Preview	Comments	Updated (UTC)
zuzagora	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	Apr 29, 2025 1:50am