-
Notifications
You must be signed in to change notification settings - Fork 5
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Auth with JWT in Convex Svelte #13
Comments
What is the normal response time on these kind of issues? This is related: #11 |
This seems to work fine? What's the Authenticate message on your websocket look like? |
Sorry about not answering earlier.
This is good, I guess, as the token is indeed sent on the wire. Sorry, I am new to Convex and Clerk. My
I can also see this in the Convex dashboard. In the Clerk-dashboard, I have created a JWT-template called "convex", and the domain in the Clerk-dashboard matches the one in the config file. Thanks so much for your time and attention, @thomasballinger |
This was resolve and was not Svelte-related. |
Solution:
I had forgotten the |
@COCPORN It'd be great to get an example into this repo of this, do you have code you'd be willing to contribute? |
@thomasballinger I think my answer has to be "Yes", a resounding yes with reservations. I understand why it is a little difficult to provide an out-of-the box example on it, as there are many moving and configurable parts here, and I personally only have a version working using Clerk and I am not super happy with the implementation of it. My implementation feels hacky still, but it works consistently. I will get to it sometime this week, if for no other reason than to have the little code needed for it pulled to pieces. |
I am running into some issues with auth using Convex Svelte. I was directed here from the Convex Discord. I feel like I am so close, so thank you for checking this out. This works:
INSIDE setAuth
is called, and shown in the log in Chrome...however...:
My "main" file looks like this:
This code is created from a discussion on Discord #general. As I mentioned above the
console.log
-line outputs a valid JWT.Thanks!
The text was updated successfully, but these errors were encountered: