We ended up caching the credentials and the JWT refresh token from Clerk, and then manually requesting the access token using the Clerk's sparsely documented frontend API. Except that to do this with Clerk, we needed to fake the cache API and then pluck the token out of the undocumented "__clerk_client_jwt" key.
replyThis is supported by Better Auth out-of-the box. It doesn't hide these kinds of stuff from you.
Sounds tough. I'd love to learn more.
replyI wasn't able to find the Better Auth docs about this use case, can you share them here please?
deleted
replyHello! I'm a mobile eng @ Clerk. Would you be open to chatting? I'd love to make this experience better for you
replySure. I added my email into the profile.
reply