allen Comments - Convex Community

@lexcodeit I'm still working through this with Convex support outside of this thread. Not experiencing some of your issues though. What version of convex auth are you using? isAuthenticatedNextjs is rather dumb, just evaluating if there is an auth token cookie present, so don't extend it too much trust. However, if everything is working properly, that token should be cleared if invalid, but you are likely evaluating it before that logic is executed.

95 replies

CCConvex Community

•Created by shea on 9/1/2024 in #support-community

IdTokenExpired on using convexAuthNextjsToken in production

95 replies

CCConvex Community

•Created by shea on 9/1/2024 in #support-community

IdTokenExpired on using convexAuthNextjsToken in production

Not sure that my component layout/structure is the culprit. seeing some similar behavior just naving around the same component layout. It will just suddenly boot me out and (this time) successfully clear cookies.

95 replies

CCConvex Community

•Created by shea on 9/1/2024 in #support-community

IdTokenExpired on using convexAuthNextjsToken in production

I'm also experiencing something thats hard to describe. Essentially in Route A with its own auth guard component in place links to Route B with different instances of the same auth guard, route B throws errors about being unauthorized, even though Route A wont present a link unless they are in a logged in state. I'm happy to hop on a call and walk through this all if its helpful.

95 replies

CCConvex Community

•Created by shea on 9/1/2024 in #support-community

IdTokenExpired on using convexAuthNextjsToken in production

My best guess is that multiple synchronous queries executing a refresh and all requesting new refresh tokens. This introduces a race condition where a stale, invalidated token can get persisted to cookie storage. This then puts everything into a bad state which there is no recovery (short of manually deleting cookies) as the bad cookie value is never cleared once identified as bad. However, this is speculative as I havent taken the time to dive into the code around this. Hopefully my uneducated musings based on observed behavior are of some help.

95 replies

CCConvex Community

•Created by shea on 9/1/2024 in #support-community

IdTokenExpired on using convexAuthNextjsToken in production

I don't know how its getting in this state, but once it is, its stuck there as nothing clears the cookie with the back refresh token value. So every request to convex tries to run a refresh routine and fails.

95 replies

CCConvex Community

•Created by shea on 9/1/2024 in #support-community

IdTokenExpired on using convexAuthNextjsToken in production

95 replies

CCConvex Community

•Created by shea on 9/1/2024 in #support-community

IdTokenExpired on using convexAuthNextjsToken in production

Feels good so far. I did get one logout and a console error of "Convex Auth: Unexpected missing refreshToken cookie during client refresh" early on, but it hasnt resurfaced. May have been some latent state from the earlier session.

95 replies

CCConvex Community

•Created by shea on 9/1/2024 in #support-community

IdTokenExpired on using convexAuthNextjsToken in production

@sshader let me know when you are ready for more testing. I reverted back to 0.0.65 due to the issue making auth state to fragile.

95 replies

CCConvex Community

•Created by oscklm on 9/17/2024 in #support-community

using _storageId vs storing storage urls directly

Video is on my roadmap too, but can cross that bridge when i get there, as it has its own special pile of concerns.

24 replies

CCConvex Community

•Created by oscklm on 9/17/2024 in #support-community

using _storageId vs storing storage urls directly

Perfect. That's actually the direction I was leaning and was considering rolling my own.

24 replies

CCConvex Community

•Created by oscklm on 9/17/2024 in #support-community

using _storageId vs storing storage urls directly

Oh nice. I'll wait for that announcement.

24 replies

CCConvex Community

•Created by oscklm on 9/17/2024 in #support-community

using _storageId vs storing storage urls directly

The position isnt unreasonable. I'm currently working on a file intensive application at the moment, so I'm interested in tracking your thinking and roadmap around this, as I'm debating where/how to host assets.

24 replies

CCConvex Community

•Created by oscklm on 9/17/2024 in #support-community

using _storageId vs storing storage urls directly

If #1 isnt a concern of the application, and the customer is on a paid plan with a custom domain setup, is #2 still a concern? Will the planned deprecation affect this use case or just shared convex.cloud customers?

24 replies

CCConvex Community

•Created by shea on 9/1/2024 in #support-community

IdTokenExpired on using convexAuthNextjsToken in production

that would make sense. I have multiple server components that would try to fetch simultaneously on app load

95 replies

CCConvex Community

•Created by shea on 9/1/2024 in #support-community

IdTokenExpired on using convexAuthNextjsToken in production

95 replies