InsForge Integrations

This skill covers integrating third-party authentication providers with InsForge. Each provider has its own guide under this directory.

Supported Providers

Common Pattern

All integrations follow the same core pattern:

1. Auth provider signs or issues a JWT containing the user's ID
2. JWT is passed to InsForge via edgeFunctionToken in createClient()
3. InsForge extracts claims via request.jwt.claims in SQL
4. RLS policies use a requesting_user_id() function to enforce row-level security

Choosing a Provider

• Clerk — Simplest setup; JWT Template handles signing, no server code needed
• Auth0 — Flexible; uses post-login Actions for claim injection
• WorkOS — Enterprise-focused; AuthKit middleware + server-side JWT signing
• Kinde — Developer-friendly; built-in token customization
• Stytch — API-first; session-based token flow

Setup

1. Identify which auth provider the project uses
2. Read the corresponding reference guide from the table above
3. Follow the provider-specific setup steps

Usage Examples

Each provider guide includes full code examples for:

• Auth provider dashboard configuration
• InsForge client utility with edgeFunctionToken
• requesting_user_id() SQL function and RLS policies
• Environment variable setup

Refer to the specific references/<provider>.md file for complete examples.

Best Practices

• All provider user IDs are strings (not UUIDs) — always use TEXT columns for user_id
• Use requesting_user_id() instead of auth.uid() for RLS policies
• Set edgeFunctionToken as an async function (Clerk) or server-signed JWT (Auth0, WorkOS, Kinde, Stytch)
• Always get the JWT secret via npx @insforge/cli secrets get JWT_SECRET

Common Mistakes