Clerk Authentication
Jazz can be integrated with Clerk to authenticate users. This method combines Clerk's comprehensive authentication services with Jazz's local-first capabilities.
How it works
When using Clerk authentication:
- Users sign up or sign in through Clerk's authentication system
- Jazz securely stores the user's account keys with Clerk
- When logging in, Jazz retrieves these keys from Clerk
- Once authenticated, users can work offline with full Jazz functionality
This authentication method is not fully local-first, as login and signup need to be done online, but once authenticated, users can use all of Jazz's features without needing to be online.
Key benefits
- Rich auth options: Email/password, social logins, multi-factor authentication
- User management: Complete user administration dashboard
- Familiar sign-in: Standard auth flows users already know
- OAuth providers: Google, GitHub, and other popular providers
- Enterprise features: SSO, SAML, and other advanced options
Implementation
We offer Clerk integration through our package: jazz-react-auth-clerk
.
After installing, use <JazzProviderWithClerk />
to wrap your app:
import * as React from "react"; import { createRoot } from "react-dom/client"; const apiKey = "you@example.com"; const PUBLISHABLE_KEY = "fake_key"; function App() { return <div>Hello World</div>; } // ---cut--- import { useClerk, ClerkProvider } from '@clerk/clerk-react'; import { JazzProviderWithClerk } from "jazz-react-auth-clerk"; function JazzProvider({ children }: { children: React.ReactNode }) { const clerk = useClerk(); return ( <JazzProviderWithClerk clerk={clerk} sync={{ peer: `wss://cloud.jazz.tools/?key=${apiKey}`, }} > {children} </JazzProviderWithClerk> ); } createRoot(document.getElementById("root")!).render( <ClerkProvider publishableKey={PUBLISHABLE_KEY} afterSignOutUrl="/"> <JazzProvider> <App /> </JazzProvider> </ClerkProvider> );
Once set up, you can use Clerk's auth methods for login and signup:
import {
SignInButton } from "@clerk/clerk-react"; import {
const SignInButton: { (props: Without<WithClerkProp<SignInButtonProps>, "clerk">): React.JSX.Element | null; displayName: string; }
useAccount,
function useAccount<A extends AccountClass<Account> | AnyAccountSchema>(AccountSchema?: A): { me: Loaded<A, true>; logOut: () => void; } (+1 overload)
function useIsAuthenticated(): boolean
useIsAuthenticated } from "jazz-react"; export functionfunction AuthButton(): React.JSX.Element
AuthButton() { const {const logOut: () => void
logOut } =useAccount(); const
useAccount<AccountClass<Account> | AnyAccountSchema>(AccountSchema?: AccountClass<Account> | AnyAccountSchema | undefined): { ...; } (+1 overload)
const isAuthenticated: boolean
isAuthenticated =function useIsAuthenticated(): boolean
useIsAuthenticated(); if (const isAuthenticated: boolean
isAuthenticated) { return <JSX.IntrinsicElements.button: React.DetailedHTMLProps<React.ButtonHTMLAttributes<HTMLButtonElement>, HTMLButtonElement>
buttonReact.DOMAttributes<HTMLButtonElement>.onClick?: React.MouseEventHandler<HTMLButtonElement> | undefined
onClick={() =>const logOut: () => void
logOut()}>Logout</JSX.IntrinsicElements.button: React.DetailedHTMLProps<React.ButtonHTMLAttributes<HTMLButtonElement>, HTMLButtonElement>
button>; } return <SignInButton />; }
const SignInButton: { (props: Without<WithClerkProp<SignInButtonProps>, "clerk">): React.JSX.Element | null; displayName: string; }
Examples
You can explore Jazz with Clerk integration in our example projects. For more Clerk-specific demos, visit Clerk's documentation.
When to use Clerk
Clerk authentication is ideal when:
- You need an existing user management system
- You want to integrate with other Clerk features (roles, permissions)
- You require email/password authentication with verification
- You need OAuth providers (Google, GitHub, etc.)
- You want to avoid users having to manage passphrases
Limitations and considerations
- Online requirement: Initial signup/login requires internet connectivity
- Third-party dependency: Relies on Clerk's services for authentication
- Not fully local-first: Initial authentication requires a server
- Platform support: Not available on all platforms