Add summary table of common auth providers (#180)

* Add summary  table of common auth providers

* Fix link

Author: benitav

installation/authentication-setup.mdx

@@ -30,7 +30,28 @@ The PowerSync client SDK uses the retrieved JWT to authenticate directly against
 
 Users are not persisted in PowerSync, and there is no server-to-server communication used for client authentication.
 
-Some authentication providers already generate JWTs for users which PowerSync can verify directly — see the documentation for individual providers (e.g. [Supabase Auth](/installation/authentication-setup/supabase-auth), [Firebase Auth](/installation/authentication-setup/firebase-auth))
+## Common Authentication Providers
+
+PowerSync supports JWT-based authentication from various providers. The table below shows commonly used authentication providers, their JWKS URLs, and any specific configuration requirements.
+
+| Provider | JWKS URL | Configuration Notes | Documentation |
+| --- | --- | --- | --- |
+| **Supabase** | Direct integration available | Uses Supabase's **JWT Secret** | [Supabase Auth Setup](/installation/authentication-setup/supabase-auth) |
+| **Firebase Auth / GCP Identity Platform** | `https://www.googleapis.com/service_accounts/v1/jwk/[email protected]` | JWT Audience: Firebase project ID | [Firebase Auth Setup](/installation/authentication-setup/firebase-auth) |
+| **Auth0** | `https://{auth0-domain}/.well-known/jwks.json` | JWT Audience: PowerSync instance URL | [Auth0 Setup](/installation/authentication-setup/auth0) |
+| **Clerk** | `https://{yourClerkDomain}/.well-known/jwks.json` |Additional configuration may be required | [Clerk Documentation](https://clerk.com/docs/backend-requests/making/jwt-templates#create-a-jwt-template) |
+| **Stytch** | `https://{live_or_test}.stytch.com/v1/sessions/jwks/{project-id}` | Additional configuration may be required | [Stytch Documentation](https://stytch.com/docs/api/jwks-get) |
+| **Keycloak** | `https://{your-keycloak-domain}/auth/realms/{realm-name}/protocol/openid-connect/certs` | Additional configuration may be required | [Keycloak Documentation](https://documentation.cloud-iam.com/how-to-guides/configure-remote-jkws.html) |
+| **Amazon Cognito** | `https://cognito-idp.{region}.amazonaws.com/{userPoolId}/.well-known/jwks.json` | Additional configuration may be required | [Cognito Documentation](https://docs.aws.amazon.com/cognito/latest/developerguide/amazon-cognito-user-pools-using-tokens-verifying-a-jwt.html) |
+| **Azure AD** | `https://login.microsoftonline.com/{tenantId}/discovery/v2.0/keys` | Additional configuration may be required | [Azure AD Documentation](https://learn.microsoft.com/en-us/entra/identity-platform/access-tokens) |
+| **Google Identity** | `https://www.googleapis.com/oauth2/v3/certs` | Additional configuration may be required | [Google Identity Documentation](https://developers.google.com/identity/openid-connect/openid-connect#discovery) |
+| **SuperTokens** | `https://{YOUR_SUPER_TOKENS_CORE_CONNECTION_URI}/.well-known/jwks.json` | Additional configuration may be required | [SuperTokens Documentation](https://supertokens.com/docs/quickstart/integrations/aws-lambda/session-verification/using-jwt-authorizer) |
+| **WorkOS** | `https://api.workos.com/sso/jwks/{YOUR_CLIENT_ID}` | Additional configuration may be required | [WorkOS Documentation](https://workos.com/docs/reference/user-management/session-tokens/jwks) |
+| **Custom JWT** | Your own JWKS endpoint | See custom auth requirements | [Custom Auth Setup](/installation/authentication-setup/custom) |
+
+## Authentication Options
+
+Some authentication providers already generate JWTs for users which PowerSync can verify directly — see the documentation for individual providers (e.g. [Supabase Auth](/installation/authentication-setup/supabase-auth), [Firebase Auth](/installation/authentication-setup/firebase-auth)).
 
 For others, some backend code must be added to your application backend to generate the JWTs needed for PowerSync — see [Custom](/installation/authentication-setup/custom) authentication.
 

installation/authentication-setup/auth0.mdx

@@ -1,6 +1,7 @@
 ---
 title: "Auth0"
 mode: wide
+description: "Setting up Auth0 Authentication with PowerSync"
 ---
 
 On Auth0, create a new API:

installation/authentication-setup/firebase-auth.mdx

@@ -1,6 +1,7 @@
 ---
 title: "Firebase Auth"
 mode: wide
+description: "Setting up Firebase Authentication with PowerSync"
 ---
 
 Configure authentication on the PowerSync instance with the following settings: