콘텐츠로 건너뛰기
Capgo

Supabase Integration Introduction

이 콘텐츠는 아직 귀하의 언어로 제공되지 않습니다.

Overview

Section titled “Overview”

This tutorial will guide you through setting up Supabase Authentication with the Capacitor Social Login plugin. This integration allows you to use native social login providers (Google, Apple, Facebook, Twitter) on mobile platforms while leveraging Supabase Auth for backend authentication and PostgreSQL for data storage.

What You’ll Learn

Section titled “What You’ll Learn”
  • How to configure Supabase Authentication
  • How to integrate Capacitor Social Login plugin with Supabase Auth
  • Platform-specific setup for Android, iOS, and Web
  • How to handle nonces securely for Supabase

What You’ll Need

Section titled “What You’ll Need”

Before you begin, make sure you have:

  1. A Supabase Project

    • Create a project at Supabase Dashboard
    • Enable Google OAuth provider
    • Get your Supabase project URL and anon key

  2. Supabase JS SDK

    • Install Supabase in your project:
      Terminal window
      npm install @supabase/supabase-js

  3. A Capacitor Project

    • An existing Capacitor application
    • Capacitor Social Login plugin installed:
      Terminal window
      npm install @capgo/capacitor-social-login
      npx cap sync

  4. Platform-Specific Google Setup

Example Application

Section titled “Example Application”

A complete working example is available in the repository:

Code Repository: You can find the code repository here

The example app demonstrates:

  • Email/password authentication with Supabase
  • Google Sign-In integration (Android, iOS, and Web)
  • A simple key-value store using Supabase PostgreSQL tables
  • User-specific data storage with Row Level Security (RLS)

Key Implementation Details

Section titled “Key Implementation Details”

Nonce Handling

Section titled “Nonce Handling”

Supabase requires special nonce handling for security. The implementation follows the React Native Google Sign In documentation:

  • Generate a rawNonce (URL-safe random string)
  • Hash it with SHA-256 to get nonceDigest
  • Pass nonceDigest to Google Sign-In
  • Pass rawNonce to Supabase (Supabase hashes it internally for comparison)

JWT Validation

Section titled “JWT Validation”

The example implementation includes JWT validation to ensure:

  • The token audience matches your configured Google Client IDs
  • The nonce matches the expected digest
  • Automatic retry on validation failure (especially important for iOS)

Platform-Specific Considerations

Section titled “Platform-Specific Considerations”
  • iOS: Token caching can cause nonce issues - the implementation handles this automatically
  • Web: Must call isLoggedIn() on mount to handle OAuth redirects
  • Android: Standard implementation with SHA-1 fingerprint configuration

Next Steps

Section titled “Next Steps”

Continue with the setup guides: