When changing domain: Need to update every users.tokenIdentifier?
Let's say I use Clerk and have a
users table with a tokenIdentifier column that is constructed as issuer|subject.
If I were to change the domain name of my website, and so change the issuer in the JWT Template in the Clerk console, does that mean that I would also need to update the users.tokenIdentifier column for each document in the users Convex database table? Seems like I would need to change the issuer component of that tokenIdentifier value.
Upon changing my domain in my issuer value in the JWT template in Clerk, I realized that ctx.auth.getUserIdentity() calls will return the new domain value, and so will not be able to query the Convex DB on users.tokenIdentifier column2 Replies
I think the answer is yes. Seems like there’s certainly production downtime, and it could be significant if one is not aware of each step for the domain name (and so dns record) change
Yup. You can stay online but it requires a proper online migration. See Stack articles on the topic.