# \[Archive\] PNP -\> SFA migration (About Dashboard Setting)

**URL:** <https://builder.metamask.io/t/archive-pnp-sfa-migration-about-dashboard-setting/1875>\
**Category:** Embedded Wallets (Web3Auth)\
**Created:** [July 19, 2023, 12:08am UTC](https://builder.metamask.io/t/archive-pnp-sfa-migration-about-dashboard-setting/1875 "2023-07-19T00:08:20Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![bjkim](https://avatars.discourse-cdn.com/v4/letter/b/57b2e6/32.png) [@bjkim](https://builder.metamask.io/u/bjkim)\
**Post date:** [July 19, 2023, 12:08am UTC](https://builder.metamask.io/t/archive-pnp-sfa-migration-about-dashboard-setting/1875/1 "2023-07-19T00:08:20Z")

</div>

> **🏛 Archived Content from Web3Auth Community**
> 
> This topic was originally posted by **bjkim** on 7/19/2023.  
> This content has been migrated from our previous community forum to preserve valuable discussions.

* * *

We previously used Google as Login Provider for Custom Auth in PNP No modal.

used like this:

[![image](https://canada1.discourse-cdn.com/flex011/uploads/metamaskbuilderhub/original/2X/5/5e12e90c77d7bb9f74e4db88b1322366b9bd70f4.png)
image811×692 38.1 KB
](https://web3auth.io/community/uploads/default/original/2X/2/26a0f0942edf8659af4fe03d4ef1e77c49198438.png "image")

However, it seemed that CustomAuth Verifier (Login Provider: Google) could not be used when switching to SFA.

[![image](https://canada1.discourse-cdn.com/flex011/uploads/metamaskbuilderhub/original/2X/e/e1a70a6d52eae9e72cb8755876fce12f478073e1.png)
image1114×118 18.7 KB
](https://web3auth.io/community/uploads/default/original/2X/f/f3c970f5640630154ca84d1f04f3e73fbcf06ae7.png "image")

When configuring SFA, should JWT be configured by itself after setting Verifier’s LoginProvider to Custom?

like this??

[![image](https://canada1.discourse-cdn.com/flex011/uploads/metamaskbuilderhub/original/2X/2/2b2edc303acc7e54b533af408f914f4ba980721c.png)
image819×740 51.6 KB
](https://web3auth.io/community/uploads/default/original/2X/d/dc8d4cd15404b49f8467145218e7b79735762549.png "image")

Or can I use it with Login Provider set to Google?

---

<div class="post-metadata">

**Author:** ![vjgee](https://avatars.discourse-cdn.com/v4/letter/v/b5e925/32.png) [@vjgee](https://builder.metamask.io/u/vjgee)\
**Post date:** [July 19, 2023, 3:56am UTC](https://builder.metamask.io/t/archive-pnp-sfa-migration-about-dashboard-setting/1875/2 "2023-07-19T03:56:17Z")

</div>

@bjkim Thanks for your recent post.

Your request has been forwarded to our team and we will get back before the updates.

---

<div class="post-metadata">

**Author:** ![tai.nguyen](https://avatars.discourse-cdn.com/v4/letter/t/3bc359/32.png) [@tai.nguyen](https://builder.metamask.io/u/tai.nguyen)\
**Post date:** [July 21, 2023, 4:21am UTC](https://builder.metamask.io/t/archive-pnp-sfa-migration-about-dashboard-setting/1875/3 "2023-07-21T04:21:31Z")

</div>

It’s possible to migrate from PnP to SFA, but it only works for those users who have not enabled MFA. Please set `usePnPKey: "true"` when instantiating the Web3Auth ([Initializing Core Kit SFA Web SDK | Documentation | Web3Auth](https://web3auth.io/docs/sdk/core-kit/sfa/initialize#usage-example)).

You can reuse the Custom Auth verifier with Google login provider in SFA. You need to pass `idToken` from Google login as a param to method `connect()` ([Usage of Core Kit SFA Web SDK | Documentation | Web3Auth](https://web3auth.io/docs/sdk/core-kit/sfa/usage#example))

The error `Error occurred while verifiying params: email not equal to body.email...` seems that idToken sent is not valid.

---

<div class="post-metadata">

**Author:** ![bjkim](https://avatars.discourse-cdn.com/v4/letter/b/57b2e6/32.png) [@bjkim](https://builder.metamask.io/u/bjkim)\
**Post date:** [July 24, 2023, 2:10am UTC](https://builder.metamask.io/t/archive-pnp-sfa-migration-about-dashboard-setting/1875/4 "2023-07-24T02:10:11Z")

</div>

The sub value when decrypting the idToken provided by google was a specific Id value. (ex . sub: 116238938292893090}

However, since I did not enter this value(sub) and directly entered the e-mail received in the verifierId, the login was successful.

it works!

```auto
    const web3authSfaprovider = await web3authSFAuth.connect({
        verifier: 'custom-auth-verifier',
        verifierId: 'my@myemail.com',
        idToken: '${Google idToken}',
    });

```

And since usePnpKey is set, the same value as the previously used wallet address is obtained.  
THX 🙂