[Archive] Switching from SFA to MFA using Core Kit

[david.hernando]

Archived Content from Web3Auth Community

This topic was originally posted by david.hernando on 11/21/2023.
This content has been migrated from our previous community forum to preserve valuable discussions.

---

In this guide you mention two approaches to switch from SFA to MFA. The guide only covers the second approach. Where do I find more information about the first one? i.e. using the Core Kit and the application handles both accounts states (SFA and MFA) during login.

[vjgee]

@david.hernando Thanks for your recent post

Your request has been forwarded to our team and we will get back to you with further updates.

[david.hernando]

@vjgee any update from team?

[maharshi]

If you wish to go from SFA to MFA, you can switch to our PnP SDKs with useCoreKitKey flag as true. Please note that the verifier, client ID, authentication method should be the same and the above mentioned flag needs to be true in order to receive the same keys.
For example, if you perform authentication via Auth0 using Google login in your SFA app. If you wish to switch to PnP no modal sdk with MFA enabled. In order for your users to receive the same keys you will have to use the same verifiers, clientID as the SFA app and Google login using auth0(same clientid) in order to get the same keys.

[david.hernando]

Thanks for your answer @maharshi . I have successfully tested the migration from SFA to MFA using @web3auth/no-modal.

Now, what I’m trying to do is to migrate from SFA to MFA using Core Kit to be able to implement our own UI for MFA instead of using the default UI in https://auth.web3auth.io popup.

According to the guide linked to the original post, there are two ways to switch from SFA to MFA, and one is Core Kit. But I’d need some guidance to achieve it.

Currently, there are two ways to achieve this:

• First is using the Core Kit approach where the application itself handles both states of the user’s accounts.
• The second** approach is a hybrid approach where the application handles the user’s account state without MFA, and the account state with MFA is handled by web3auth SDK by redirecting to openlogin.

[david.hernando]

@maharshi @vjgee I managed to import the account obtained with SFA SDK into Core Kit tKey SDK. But how do I mark a verifier id as upgraded so that it cannot be used with SFA SDK anymore?

[maharshi]

Hey @david.hernando
Can you please confirm if you’re you referring to using the import flow in tKey?

[david.hernando]

Hi @maharshi , the final goal is to move an account from SFA to tKey. I’m not sure if the import flow is the right approach or there is another way.

With the import flow I’ve been able to import the private key from the SFA SDK to the ThresholdKey SDK. However, that process does not invalidate the usage of SFA SDK for the same verifierId.

On the other hand, in this guide, when MFA is enabled with NoModal SDK, the usage of SFA SDK is invalidated and the connect() methods throws an error.

In the end, what we want to achieve is the same possibility to switch from SFA to MFA shown in the guide but using CoreKit all the time to design our own UI/UX to enable and manage the additional shares.

[david.hernando]

@maharshi @vjgee can you help with this topic?

[shahbaz]

@david.hernando

the final goal is to move an account from SFA to tKey. I’m not sure if the import flow is the right approach or there is another way.

Hey @david.hernando

Have you used SfaServiceProvider flow?

  <a href="https://github.com/Web3Auth/web3auth-core-kit-examples/blob/main/tkey-web/quick-starts/tkey-react-quick-start/src/App.tsx" target="_blank" rel="noopener">github.com</a>

Web3Auth/web3auth-core-kit-examples/blob/main/tkey-web/quick-starts/tkey-react-quick-start/src/App.tsx

  <pre><code class="lang-tsx">import { useEffect, useState } from "react";

import { tKey, chainConfig } from ‘./tkey’;
import { ShareSerializationModule } from ‘@tkey/share-serialization’;
import { SfaServiceProvider } from ‘@tkey/service-provider-sfa’;
import { WebStorageModule } from ‘@tkey/web-storage’;
import { Web3 } from ‘web3’;
import { EthereumPrivateKeyProvider } from ‘@web3auth/ethereum-provider’;
import { IProvider } from “@web3auth/base”;

// Firebase libraries for custom authentication
import { initializeApp } from “firebase/app”;
import { GoogleAuthProvider, getAuth, signInWithPopup, UserCredential } from “firebase/auth”;

import “./App.css”;

const verifier = “w3a-firebase-demo”;

// Your web app’s Firebase configuration
const firebaseConfig = {
apiKey: “AIzaSyB0nd9YsPLu-tpdCrsXn8wgsWVAiYEpQ_E”,

This file has been truncated. show original

The SFA configs will be used with tKey allowing you to bring SFA users to tKey( adding multiple factors, enabling MFA).

[david.hernando]

Hey @shahbaz , thanks for your answer.

Yes, I’ve tried with SfaServiceProvider . But I get a different private key than with @web3auth/single-factor-auth. I need to preserve the same key from SFA on tKey.

And also disable SFA for that verifierId. Exactly as you do on the guide referred previously when using @web3auth/no-modal. But with Core Kit.

Thanks for your help.

[shahbaz]

Hey @david.hernando

Thanks for reporting it. Let me report it to the team.

This is supposed to work seamlessly. Let me get back to you when I have some updates on this.

[david.hernando]

@shahbaz did you get feedback from your team?

Any hint on how can I delete nonce in Torus nodes to disable SFA ?

[shahbaz]

Hey @david.hernando

Apparently, it is taking longer than expected. Our team will follow up on this as soon as it is released from our end.