Moving from default verifiers to custom verifiers - can we retain/import existing keys?

We would like to migrate from the no-modal SDK to the single-factor-auth SDK.

Currently we’re using the No-Modal-sdk using no custom verifier, and we have already about 1700 active wallets using it.

We would like to migrate to use the Single Factor Auth SDK to also minimize overhead and customize the user experience.

We’ve already implemented it locally and we noticed that now that of course users with the same google account as before do have a new key and therefor can’t log into their existing accounts.

So we’re wondering if there is a way to migrate to the SFA SDK but make sure all the users we already have will still be able to log in with their google/apple etc. accounts.

In a different thread there was the talk about this maybe being a possibility using aggregate verifiers, which we looked into but when we set it up, it would of course ask for a custom google-appId for the google part, in which case we’re assuming that it also will NOT let the existing users log into their accounts.

So the questions would be:

  1. Is it possible to migrate/import existing users/keys from the default verifier into a new custom jwt verifier so that those users then still can log in.

  2. if 1 is not possible, is it possible to switch to the single factor auth SDK using aggregate verifiers so existing users can still log into their accounts, and if so, how exactly would this then needed to be set up beyond the existing documentation on how to create aggregate verifiers.

Thank you.

@circleslandnow Thanks for your recent communication.

Your request has been forwarded to our team and we will get back with further updates once more information becomes available.

After checking with our team, it is not possible.

okay. that’s unfortunate.
Thank you very much.