Is Authenticated function required to integrate convex with clerk?
If so, it should be explicit and emphasized. Common mistakes in my team.
7 Replies
Thanks for posting in <#1088161997662724167>.
Reminder: If you have a Convex Pro account, use the Convex Dashboard to file support tickets.
- Provide context: What are you trying to achieve, what is the end-user interaction, what are you seeing? (full error message, command output, etc.)
- Use search.convex.dev to search Docs, Stack, and Discord all at once.
- Additionally, you can post your questions in the Convex Community's <#1228095053885476985> channel to receive a response from AI.
- Avoid tagging staff unless specifically instructed.
Thank you!
I found Authenticated be in one documentation page, on step 9. It’s not completely clear whether it is required
This is the <Authenticated> component that only renders once Convex has sent auth info from the client? It's the most common way to allow both authed and unauthed states on the same page, so if you're doing that it's pretty useful.
Step 9 seems like the right place for it, sounds like walking through why it's useful / what happens if you don't use it would be belpful
Yes I think that’s the component
So is isAuthenticated required as well then (for both an auth and unauthenticated state on the same page)?
Convex & Clerk | Convex Developer Hub
Clerk is an authentication platform providing login via
IsAuthenticated is mentioned toward the bottom but it’s not part of the explicit steps
These docs seem to imply isAuthenticated is required to use with Authenticated. Otherwise, the app might get into a bad state
None of this is required, but if you want to avoid running queries until the client is has authenticated then either
<Authenticated> component or conditionals using isAuthenticated can be used.