@jamwtIn the Custom Auth docs, is the
@JamieIn the Custom Auth docs, is the Server Side the important part? Because it feels like the Client side is tightly geared to React still which seems to defeat the purpose of custom auth. Can you add some clarification here because I've gotten custom auth working on the server side but what I and lots of other people seem to run into is that no auth platform have the same approach, and so is I'm already tied to say Svelte, but I want to use WorkOS, that Custom Auth is great for my use case.
1 Reply
Hey @MergeTree Maxxer, the server side part is essential for any type of client to work with Convex's built-in auth support (
ctx.auth). The client-side is indeed specific to React, and if you're using ConvexClient or ConvexHTTPClient (or the Python or Rust clients) you can adapt it (and it'll be progressively simpler than React). The client-side part is really about how the client knows the JWT token to pass back to the server.