Skip to content

Commit d59c927

Browse files
authored
Supabase auth workaround (#42)
1 parent 7c6b891 commit d59c927

File tree

4 files changed

+16
-0
lines changed

4 files changed

+16
-0
lines changed

installation/authentication-setup/supabase-auth.mdx

Lines changed: 4 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -17,6 +17,10 @@ You can implement various types of auth:
1717
* [Example](https://github.com/powersync-ja/powersync-jwks-example/)
1818
* Experimental: We've also heard from the community that Supabase's newly released [support for external auth providers works](https://supabase.com/blog/third-party-auth-mfa-phone-send-hooks), but we don't have any examples for this yet.
1919

20+
<Note>
21+
The "Supabase Auth" setting no longer works for Supabase projects created after 25 November 2024. While we are working with Supabase on a fix, please apply this workaround: https://releases.powersync.com/announcements/important-notice-for-supabase-users-using-supabase-jwts
22+
</Note>
23+
2024
To implement either Supabase Auth or Anonymous Sign-Ins, enable the "Use Supabase Auth" setting on the PowerSync instance. (This is also [covered in the Supabase & PowerSync integration guide](/integration-guides/supabase-+-powersync#configuring-powersync))
2125

2226
Internally, Supabase auth signs the token using HS256, using a secret available as `current_setting('app.settings.jwt_secret')` on the database.

installation/database-connection.mdx

Lines changed: 4 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -38,6 +38,10 @@ Select your Postgres hosting provider for steps to connect your Postgres databas
3838
2. Under the **"Client Auth"** tab, enable **"Use Supabase Auth".**
3939
3. Click **"Save".**
4040

41+
<Note>
42+
The "Supabase Auth" setting no longer works for Supabase projects created after 25 November 2024. While we are working with Supabase on a fix, please apply this workaround: https://releases.powersync.com/announcements/important-notice-for-supabase-users-using-supabase-jwts
43+
</Note>
44+
4145
PowerSync deploys and configures an isolated cloud environment for you, which can take a few minutes to complete.
4246

4347
### Troubleshooting

integration-guides/flutterflow-+-powersync.mdx

Lines changed: 4 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -100,6 +100,10 @@ It is important to uncheck this checkbox
100100
2. Under the **"Client Auth"** tab, enable **"Use Supabase Auth".**
101101
3. Click **"Save".**
102102

103+
<Note>
104+
The "Supabase Auth" setting no longer works for Supabase projects created after 25 November 2024. While we are working with Supabase on a fix, please apply this workaround: https://releases.powersync.com/announcements/important-notice-for-supabase-users-using-supabase-jwts
105+
</Note>
106+
103107
PowerSync deploys and configures an isolated cloud environment for you, which will take a few minutes to complete.
104108

105109
### Configure Sync Rules

integration-guides/supabase-+-powersync.mdx

Lines changed: 4 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -138,6 +138,10 @@ It is important to uncheck this checkbox
138138
</Frame>
139139
8. Click **"Save".**
140140

141+
<Note>
142+
The "Supabase Auth" setting no longer works for Supabase projects created after 25 November 2024. While we are working with Supabase on a fix, please apply this workaround: https://releases.powersync.com/announcements/important-notice-for-supabase-users-using-supabase-jwts
143+
</Note>
144+
141145
PowerSync deploys and configures an isolated cloud environment for you, which will take a few minutes to complete.
142146

143147
### Configure Sync Rules

0 commit comments

Comments
 (0)