Privy

[julien51]

Description

A couple of months ago, we introduced Unlock Accounts 2.0 to improve our existing Unlock Accounts. At the time, the main goal was to add support for Google and Email magic links to existing passwords. For this we use Coinbase's wallet as a service... but they are deprecating this so we need to replace that.
We decided to go with Privy which offers a few benefits (mostly they manage everything so we don't have to worry about much), but that also presents 2 challenges:

• first one is rather easy to solve. Normally Privy loads as a modal. We need to be able to also "embed" their UI so that it does not use a modal because our checkout is already a modal (and a modal in a modal would be bad UI). Luckily they recently added support for that thru _render: { standalone: true, } option when loading it.
• the second one is a bit more challenging. Currently, in order to perform API calls, we generate a JWT token from a signed SIWE message. Since Privy already asks for a SIWE message, we should not ask for a 2nd signature. Luckily, Privy already provides a JWT that we could use. This means locksmith will need to support both our legacy tokens (because that is what our API uses) and the Privy tokens.

Custom checklist:

A test plan for the newly integrated auth system, focusing on different authentication methods using Privy:

1. Email Authentication:
   • User enters email address
   • User receives one-time password (OTP)
   • User enters OTP to authenticate
   • Verify successful login and access to checkout
   • Checkout (unlock-protocol.com domain)
     • Make a purchase
     • Save metadata
     • Network swicth
   • Embedded Paywall & provider (loaded from 2rd party site, for example dirt.fyi)
     • Make a purchase
     • Save metadata
     • Network switch

• Dashboard
  • check user settings (save CC)
  • Deploy lock (probably won't work because no gas)
  • Update Lock settings
  • Network switch
• OAuth flow
  • can login on ouvre-boite.com
• Events
  • RSVP free event
  • RSVP paid event (with CC)
• Keychain
  • Add to Mobile wallet (iOS or Android)

2. Wallet Authentication (Sign In With Ethereum):
   • User connects their wallet
   • User signs the authentication message
   • Verify successful login and access to checkout
   • Checkout
     • Make a purchase
     • Save metadata
     • Network switch
   • Embedded Paywall
     • Make a purchase
     • Save metadata
     • Network switch

• Dashboard
  • check user settings (save CC)
  • Deploy lock
  • Update Lock settings
  • Network switch
• OAuth flow
  • can login on ouvre-boite.com
• Events
  • Create event
  • RSVP free event
  • RSVP paid event (with CC)
  • RSVP paid event (with crypto)
• Keychain
  • Add to Mobile wallet (iOS or Android)
• Certification
  • CReate a certification
  • Airdrop certifications
• Subscription
  • Create a subscription

3. Error Handling:
   • Test with invalid credentials for each auth method
   • Verify appropriate error messages are displayed

[julien51]

This is not needed :)

[julien51]

This is what makes the privy load inside a component rather than as a modal.

[0xTxbi]

necessary configs for privy on locksmith.