Torus OpenLogin LoginConfig for Social Logins doesn't allow me to remove twitter from modal

Help - Plug n Play
1

Hi,

I was recently playing around with the OpenLogin LoginConfigs (Initialization | Documentation) and tried removing all social logins to only have Google and Email showing.

It worked great for all social to classify showOnModal = false. However, when I also did this for twitter, it didn’t change anything. The Twitter login always remained. Do you know if I need to change something else. I tried turning all configs for twitter to false but it still showed.

Let me know if you need more information.
Thanks guys!

3

Hi there could you provide more information about the sdk that you’re using?

4

Hi naveed,

Thanks for your response!

I stand corrected from my initial link to the documentation. It is actually about the Torus embed SDK. The issues seem to stem from @toruslabs/torus-embed where we are trying to specify the loginConfic argument in the init function. We are running "@toruslabs/torus-embed": "^1.36.5",

Let me know if you need more information.
Best C

5

Below how I am currently trying to implement it. Maybe you have a proposition how to differently do it:

        await torus.init({
          showTorusButton: false,
          whiteLabel,
          loginConfig: {
            twitter: {
              name: 'twitter',
              typeOfLogin: 'twitter',
              showOnModal: false,
            },
            facebook: {
              name: 'facebook',
              typeOfLogin: 'facebook',
              showOnModal: false,
            },
            discord: {
              name: 'discord',
              typeOfLogin: 'discord',
              showOnModal: false,
            }
          },

          network: {
            host: networkConfigTorus(),
          },
        });

It works fine for all other social logins that I am trying to remove. Somehow only Twitter is resistant to being removed.

Screenshot 2023-03-30 at 15.44.35
Screenshot 2023-03-30 at 15.44.351016×1478 106 KB

6

@naveed Do you have any recommendations for this? Still an issue

7

This topic was automatically closed 60 days after the last reply. New replies are no longer allowed.

8
9

@clemens You can look at the below code snippet:

import { Web3Auth } from "@web3auth/modal";
import { CHAIN_NAMESPACES, WALLET_ADAPTERS } from "@web3auth/base";

const web3auth = new Web3Auth({
  chainConfig: { chainNamespace: CHAIN_NAMESPACES.EIP155 },
  clientId: "BPi5PB_UiIZ-cPz1GtV5i1I2iOSOHuimiXBI0e-Oe_u6X3oVAbCiAZOTEBtTXw4tsluTITPqA8zMsfxIKMjiqNQ",
  web3AuthNetwork: "sapphire_mainnet",
});

await web3auth.initModal({
  modalConfig: {
    [WALLET_ADAPTERS.OPENLOGIN]: {
      label: "openlogin",
      loginMethods: {
        // Disable facebook and twitter
        facebook: {
          name: "facebook",
          showOnModal: false,
        },
        twitter: {
          name: "twitter",
          showOnModal: false,
        },
      },
    },
  },
});
10

The latest version for @toruslabs/torus-embed is 4.0.4. Could you please upgrade and let me know if you still face this issue?

11

Thanks guys this has been resolved! Just FYI, we are still using Torus for that. the code snipped from @vjgee applies but it uses Torus.init.

That also means we don’t have a client ID and specify the web3AuthNetwork or wallet_adapters label.

12

This topic was automatically closed 2 days after the last reply. New replies are no longer allowed.