Hi there, I’ve got a question around recipe user id usage for email verification please as I’m not sure if there is a bug in
getUser
or I just don’t understand how user id mapping is supposed to work between recipe user ids and external ids.
Currently we’re mapping our users to an external id with
createUserIdMapping
after signing them up. We then verify their emails using the external id as it’s the id returned by calling
getUser
. Once the email is verified, a row is added to
emailverification_verified_emails
with the external user id as the
user_id
in the database.
This works well as the email verification claim
st-ev
is
true
in the access token jwt and if I call
isEmailVerified
with the external user id converted to a recipe user id then it returns true.
The problem seems to be with
getUser
as it returns a list of
loginMethods
but the
verified
flag is false even though
isEmailVerified
returns true if I check using the same
recipeUserId
and email returned in the login method. The email verification claim for this user is
true
in the access token too.
However if I change the logic to verify the email based on the supertokens user id instead, then
getUser
will return the login method
verified
as true but the email verification claim
st-ev
is false.
I may be misunderstanding how the different ids are supposed to be used but it seems like
getUser
may be returning the verification status of the email login method incorrectly please?
