Mapping telegram user ids to Convex users
is there a way to just tell Convex "this user is authenticated" and then call the actions and have
ctx.auth.getUserIdentity() return the user?
I have a use case for telegram bot where I am looking up user by their telegram user id and then calling the actions that depend on ctx.auth.getUserIdentity().
I want to avoid the need to pass telegram user id to the convex actions and want to have the same experience for telegram users as a user calling via convex react client.
I am using Clerk as auth provider and have users synced users between users table and Clerk. users tables has telegramUserId field which I am using for looking up user when handling webhook requests4 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 don't remember the specifics but I walked through similar requirements with another user integrating with Telegram here, I believe they got everything working. Used Clerk. https://discord.com/channels/1019350475847499849/1317824540818276412
i think my question is a bit different as there is no client side involved here. The request lands on convex http action from telegram servers as webhook and there we don't have any jwt attached to the request but only signature which can verify the origin of request and after that we use telegramUserId in the request to associate the request to the user.
I think I need to create a reverse proxy that handles the webhook and use clerk api to generate the session token for the user identified by telegram user id and then relay the request with jwt token to convex http action.
I was wondering if this would make a useful feature in Convex where we could manually set authentication context just like other backend frameworks like Spring
This really isn't much different from the standard authenticated webhook scenario. Would be cool to override as a part of the client library, but it is possible to do without that. If your api is generally accessible both directly to authenticated users and indirectly through webhooks (as opposed to just webhooks, which is an even simpler scenario), what I do is use a helper function that creates an authentication object defining authorization. It can either use the authenticated user, or accept an override user id, and spit out the same kind of authorization object either way. Your functions use the authorization object rather than relying directly on built in authentication.
I mean you don't even need it to be an authorization object really, the helper function could just return the user id and accept an override.
I'd also go further and say most apps should be using their own function to wrap
getAuthUserId() or whatever your core auth function is. You're going to want to customize that behavior, whether for authorization, roles, overriding, etc. From there, adding the behavior you're looking for becomes somewhat trivial.