Aggregate verifier for email configuration question

[hadeath03]

The aggregate verifier issue is explained here and now it’s working.
But it’s strange because I didn’t find the solution from web3auth-pnp-examples nor any articles. So I am not sure if I am using it correctly.

Here is the web3auth-pnp-examples code

// Not working
const loginAuth0EmailPasswordless = async () => {
    ...
    const web3authProvider = await web3auth.connectTo(WALLET_ADAPTERS.OPENLOGIN, {
      loginProvider: "auth0emailpasswordless",
      extraLoginOptions: {
        domain: "https://web3auth.au.auth0.com",
        verifierIdField: "email",
        isVerifierIdCaseSensitive: false,
      },
    });
    setProvider(web3authProvider);
  };

This code didn’t work when I applied to my project (It shows sign up UI but not email passwordless but just normal sign up that include Google and Github) and when I added connection: "email" in the extraLoginOptions object, it worked.

// Working code
const loginAuth0EmailPasswordless = async () => {
    ...
    const web3authProvider = await web3auth.connectTo(WALLET_ADAPTERS.OPENLOGIN, {
      loginProvider: "auth0emailpasswordless",
      extraLoginOptions: {
        domain: <MY-DOMAIN>,
        verifierIdField: "email",
        isVerifierIdCaseSensitive: false,
        connection: "email" // <- this make it work
      },
    });
    setProvider(web3authProvider);
  };

My question is:

1. Why web3auth-pnp-examples aggregate verifier email passworedless code works without connection: "email" while mine is not?

2. Where can I find the connection: "email" related information?

Thanks in advance

[maharshi]

Hey again @hadeath03,

Could you please provide a screenshot of the connections enabled in the Auth0 dashboard for the app corresponding to the Auth0 client ID you’re using? This will help us better understand your setup and guide you accordingly.

Additionally, you mentioned connection: email — further details on this can be found in another active thread you’ve created. We recommend checking there for related discussions and insights.