Closed nazrinharris closed 3 months ago
IIRC, the new account could either be:
bcrypt
hashing for passwordUserType
I think I'll name the old PecuniaUser
to be PecuniaUser V1
, so that means the newer version would be PecuniaUser V2
, which uses bcrypt
for local password storage and introduces UserType
.
If I'm correct, #154 introduced UserType
and #146 introduced bcrypt
.
PecuniaUser
So here's how the updating will go.
UserType
shenanigan, that is, it searches the local database to see if the current logged in user is a local user or not, and sets it accordingly.Now that I've looked into it a little bit more, it seems like maybeMigratePecuniaUser
is already handling the UserType
shenanigan, all that's left is to handle the password
Should be completed with 6926391 in #132
This doesn't need to be a full fledged feature, as this technically only applies to me.