Skip to content

Commit 87bdfbb

Browse files
authored
Documentation edits made through Mintlify web editor
1 parent 2d0d4e6 commit 87bdfbb

File tree

1 file changed

+6
-0
lines changed

1 file changed

+6
-0
lines changed

installation/authentication-setup.mdx

Lines changed: 6 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -3,6 +3,8 @@ title: "Authentication Setup"
33
sidebarTitle: Overview
44
---
55

6+
## Overview
7+
68
PowerSync clients (i.e. apps used by your users that embed the PowerSync Client SDK) authenticate against the server-side [PowerSync Service](/architecture/powersync-service) using [JWTs](https://jwt.io/) (signed tokens) that are generated by your application backend.
79

810
Before using PowerSync, an application's existing architecture may look like this:
@@ -34,6 +36,10 @@ Users are not persisted in PowerSync, and there is no server-to-server communica
3436

3537
PowerSync supports JWT-based authentication from various providers. The table below shows commonly used authentication providers, their JWKS URLs, and any specific configuration requirements.
3638

39+
<Tip>
40+
Scroll the table horizontally.
41+
</Tip>
42+
3743
| Provider | JWKS URL | Configuration Notes | Documentation |
3844
| --- | --- | --- | --- |
3945
| **Supabase** | Direct integration available | Uses Supabase's **JWT Secret** | [Supabase Auth Setup](/installation/authentication-setup/supabase-auth) |

0 commit comments

Comments
 (0)