Token auth failing depending on username: fixed in nightly
What was going on
Issue surrealdb/surrealdb#2963 (closed, 22 comments): On a websocket connection, after signin, taking the token to authenticate sometimes fails depending on the username. Scope defined with SIGNUP (CREATE user with crypto::argon2::generate) and SIGNIN (SELECT * FROM user WHERE user = $user AND crypto::argon2::compare(pass, $pass)). After creating a user, token authentication intermittently fails based on which username was used.
The fix
Scoped token authentication failing inconsistently depending on the username was a server bug in SurrealDB, not your scope definition: the fixing PR was merged and shipped in the next nightly. If signin works but the returned token sometimes fails depending on the username, upgrade to a nightly build that includes the fix.