More supabase auth references

Author: benitav

self-hosting/appendix/database-connection.mdx

@@ -8,33 +8,34 @@ Below, you can find provider-specific instructions to obtain connection details
 
 <AccordionGroup>
   <Accordion title="Supabase">
-1. In your Supabase dashboard, navigate to **"Project Settings"** \-> **"Database" -> "Connection string**" and select the "URI" tab.
-2. Uncheck the "**Display connection pooler**" checkbox. PowerSync needs to connect to the database directly and cannot use the pooler.
-
-<Frame>
-  <img src="/images/self-hosting-3.avif"/>
-</Frame>
-1. Copy the connection string. The hostname should be `db.<PROJECT-ID>.supabase.co`, and not, for example, `aws-0-us-west-1.pooler.supabase.com`.
-2. Paste this URI into the `uri` field under `replication` \> `connections` in your configuration file, for example:
-
-```yaml
-# config.yaml
-
-replication:
-  connections:
-    - type: postgresql
-      uri: postgresql://postgres:[YOUR-PASSWORD]@db.abc.supabase.co:5432/postgres
-```
-
-1. Replace `[YOUR-PASSWORD]` with the password for the `postgres` user in your Supabase database.
-   * Supabase also [refers to this password](https://supabase.com/docs/guides/database/managing-passwords) as the _database password_ or _project password_.
-2. PowerSync has the Supabase CA certificate pre-configured — `verify-full` SSL mode can be used directly, without any custom certificates.
-3. Under `client_auth` enable Supabase Auth:
-
-```yaml
-client_auth:
-  supabase: true
-```
+    1. In your Supabase dashboard, navigate to **"Project Settings"** \-> **"Database" -> "Connection string**" and select the "URI" tab.
+    2. Uncheck the "**Display connection pooler**" checkbox. PowerSync needs to connect to the database directly and cannot use the pooler.
+    <Frame>
+      <img src="/images/self-hosting-3.avif"/>
+    </Frame>
+    3. Copy the connection string. The hostname should be `db.<PROJECT-ID>.supabase.co`, and not, for example, `aws-0-us-west-1.pooler.supabase.com`.
+    4. Paste this URI into the `uri` field under `replication` \> `connections` in your configuration file, for example:
+
+    ```yaml
+    # config.yaml
+
+    replication:
+      connections:
+        - type: postgresql
+          uri: postgresql://postgres:[YOUR-PASSWORD]@db.abc.supabase.co:5432/postgres
+    ```
+
+    5. Replace `[YOUR-PASSWORD]` with the password for the `postgres` user in your Supabase database.
+      * Supabase also [refers to this password](https://supabase.com/docs/guides/database/managing-passwords) as the _database password_ or _project password_.
+    6. PowerSync has the Supabase CA certificate pre-configured — `verify-full` SSL mode can be used directly, without any custom certificates.
+    7. Under `client_auth` enable Supabase Authentication:
+
+    ```yaml
+    client_auth:
+      supabase: true
+      supabase_jwt_secret: [secret]
+    ```
+    For more details, see [Supabase Auth](/installation/authentication-setup/supabase-auth).
   </Accordion>
   <Accordion title="AWS RDS">
 Add your connection details under `replication` \> `connections` in your configuration file.

self-hosting/installation/client-side-setup.mdx

@@ -97,14 +97,15 @@ If you are using Supabase or Firebase authentication, PowerSync can verify JWTs
 
 ### Supabase Auth
 
-Under `client_auth` in your config file, enable `supabase` authentication:
+Under `client_auth` in your config file, enable Supabase authentication:
 
 ```yaml
 # config.yaml
 
 client_auth:
   # Enable this if using Supabase Auth
   supabase: true
+  supabase_jwt_secret: [secret]
 ```
 
 For more details, see [Supabase Auth](/installation/authentication-setup/supabase-auth).