insforge-integrations

To set up JWT-based authentication and row-level security, you must configure your provider's token flow to issue JWTs via edgeFunctionToken and apply SQL policies using the requesting_user_id() function to enforce RLS access control.

Yes, you can use Clerk or Auth0 to handle authentication across microservices. The integration standardizes how providers issue JWTs to InsForge via edgeFunctionToken, maintaining a consistent authentication context for your applications.

Supported providers for third-party auth integration include Clerk, Auth0, WorkOS, Kinde, and Stytch. Each provider features specific setup guides detailing unique token-signing flows and SQL policies for consistent RLS enforcement.

Edge function tokens enforce RLS policies by standardizing how authentication providers pass JWTs to InsForge. The SQL function requesting_user_id() then extracts the user identity from the edgeFunctionToken to apply consistent row-level security access control.

You need the requesting_user_id() SQL function to extract user identity from the edgeFunctionToken JWT. It serves as the required mechanism to evaluate SQL policies and strictly enforce row-level security access control across your applications.

Yes, InsForge supports custom token flows for WorkOS and Stytch. Provider-specific references cover unique setup requirements, ensuring each provider correctly issues or passes JWTs via edgeFunctionToken for consistent RLS enforcement.