Page MenuHomePhabricator

[identity] check users table before reserved usernames table for user ID during wallet login
ClosedPublic

Authored by varun on Jul 21 2024, 12:04 PM.
Tags
None
Referenced Files
Unknown Object (File)
Fri, Nov 1, 10:57 AM
Unknown Object (File)
Fri, Nov 1, 10:57 AM
Unknown Object (File)
Fri, Nov 1, 10:57 AM
Unknown Object (File)
Fri, Nov 1, 10:57 AM
Unknown Object (File)
Thu, Oct 24, 6:18 AM
Unknown Object (File)
Mon, Oct 21, 10:32 PM
Unknown Object (File)
Wed, Oct 16, 7:47 PM
Unknown Object (File)
Wed, Oct 16, 7:44 PM
Subscribers

Details

Summary

we should check the users table first in case the user ID happens to be in both tables for some reason (this should never happen, but unfortunately there was a bug that led to this rule being violated). by checking the users table first, we ensure that registered wallet users will be able to log in even if there is invalid data in the reserved usernames table.

Test Plan

add userID and wallet address to staging reserved usernames table. then successfully log in with wallet

Diff Detail

Repository
rCOMM Comm
Branch
master
Lint
No Lint Coverage
Unit
No Test Coverage

Event Timeline

Harbormaster returned this revision to the author for changes because remote builds failed.Jul 21 2024, 12:15 PM
Harbormaster failed remote builds in B30550: Diff 42597!
varun requested review of this revision.Jul 21 2024, 1:38 PM
bartek added inline comments.
services/identity/src/client_service.rs
521

you can use login_time here too

This revision is now accepted and ready to land.Jul 22 2024, 1:50 AM
This revision was landed with ongoing or failed builds.Jul 22 2024, 10:03 AM
This revision was automatically updated to reflect the committed changes.