enable MFA on the instance1 and you should be able to get backup factor which will be used to login another session
create another corekit instance (instance2) and login with backup factor you have from above step
login should be successful with instance2
from instance1 delete the backup factor, which is used to login for instance2
verify the backup factor has been successfully deleted, as well as it's related metadata (commitChanges when using manualSync:true)
from instance2, try to create new factor with the deleted backup factor
Expected Result
From instance2, new factor should not be able to created, should throw factor not present error, since the active factor key of instance2 has been deleted from instance1
Actual Result
With deleted backup key, new factor can be created locally in instance2. MPC-Corekit throws an error only when sync with metadata service.
lwin-kyaw
commented
2 months ago
Steps to reproduce -
instance1)instance1and you should be able to get backup factor which will be used to login another sessioninstance2) and login withbackup factoryou have from above stepinstance2instance1delete thebackup factor, which is used to login forinstance2backup factorhas been successfully deleted, as well as it's related metadata (commitChangeswhen using manualSync:true)instance2, try to create new factor with the deletedbackup factorExpected Result
From
instance2, new factor should not be able to created, should throwfactor not presenterror, since the active factor key ofinstance2has been deleted frominstance1Actual Result
With deleted
backup key, new factor can be created locally ininstance2. MPC-Corekit throws an error only when sync with metadata service.