How to configure Authorization to connect with own private blockchain

Help - Plug n Play
1

I’m trying to use web3 Auth with my private blockchian and I’d like to add authorization.
I tryed it but not work. How I configure them?

const web3auth = new Web3Auth({
clientId,
chainConfig: {
chainNamespace: CHAIN_NAMESPACES.EIP155,
chainId: '0x-my-private-chain-id',
rpcTarget: 'https://my-privatechain-jsonRPC-url/',
headers: {
Authorization:
'Basic .............',
},
},
});
2

@fc.kikkawa Thanks for reaching out.

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

3

@fc.kikkawa Could you take a look at the below documentation on how to connect to your blockchain:

Choose Other chains when initializing

4

Thank you for your response. I have reviewed the relevant documents and set the configurations accordingly. I have set up a private blockchain with goquorum on the EVM-compatible platform Kaleido. However, when I set the ID and password as shown below, I encounter the following error: “Uncaught (in promise) Error: Failed to execute ‘fetch’ on ‘Window’: Request cannot be constructed from a URL that includes credentials.” Could you please advise how I should incorporate authentication?

I’ve also commented out the ‘headers’ section, as I was advised that it’s not necessary for the configuration.

chainConfig: {
  chainNamespace: CHAIN_NAMESPACES.EIP155,
  chainId: '0x7FE3FED8',
  rpcTarget: 'https://k0t6l5jxby:BlGk462HOn_4qRYErnBX5wnJGYg6oMnOKne5tamUSa0@k0o04npfrn-k0a3g3t8wh-rpc.kr0-aws.kaleido.io/',
  // headers: {
  //   Authorization: 'Basic azB3ZXBkeGY3czp5Ui0xRHR5aE1Odk5iLTJuMkRDVWE1X0FGdHgtdU1lclU3OWhZZ1g4eTJr',
  // },
},
5

I hope this message finds you well.

I am writing to express my interest in having a direct conversation with you, if possible. I believe this would allow us to discuss matters more effectively and have a deeper understanding of each other’s perspectives.

I look forward to the possibility of this arrangement and would greatly appreciate any opportunity to do so.

Thank you for considering my request. I am available at your earliest convenience to discuss the details.

6

Hey @fc.kikkawa

Our EVM Blockchain provider only supports public EVM Blockchains. For using any private blockchain, you have to follow the route for exporting the private key and making your own provider, which we do for non evm compatible blockchains. As @vjgee shared earlier, the common key provider will work here for you. You can have a look at our react native EVM blockchain connection where we have documented something similar: https://web3auth.io/docs/connect-blockchain/ethereum/react-native

7

Thank you for your reply.
I’m following this document but have an error
document : Connect your Blockchain | Documentation | Web3Auth

“TypeError: _this2.walletAdapters[adapterName].setChainConfig is not a function”

How could I solve this problem?
My configuration is here.

const init = async () => {
      try {
        const chainConfig = {
          chainNamespace: CHAIN_NAMESPACES.EIP155,
          chainId: '0xA',
          rpcTarget: 'https://k0o04npfrn-k0a3g3t8wh-rpc.kr0-aws.kaleido.io/',
          displayName: 'Chain Name',
          ticker: 'ETH',
          tickerName: 'Ethereum',
        };
        const web3auth = new Web3Auth({
          clientId,
          chainConfig,
          web3AuthNetwork: 'cyan',
        });

        const openloginAdapter = new OpenloginAdapter({
          adapterSettings: {
            uxMode: 'popup',
            loginConfig: {
              google: {
                verifier: 'ryukyu-web3auth', // Pass the Verifier name here
                typeOfLogin: 'google', // Pass on the login provider of the verifier you've created
                clientId:
                  '2108287..........................apps.googleusercontent.com', // Pass on the Google `Client ID` here
              },
            },
          },
        });

        setWeb3auth(web3auth);
        console.log('web3auth :', web3auth);
        web3auth.configureAdapter(openloginAdapter);
        console.log('configure adapter');
        await web3auth.initModal();
        console.log('sucsses init');
        setProvider(web3auth.provider);
      } catch (error) {
        console.error(error);
      }
    };
8

For the document “Common Provider | Documentation | Web3Auth”
How could I configure for “web3authSfaprovider” at For Single Factor Auth Web SDK. Im using google verifier. so is that looks like this?

const web3authSfaprovider = await web3auth.connect({
  google: {
                verifier: 'ryukyu-web3auth', // Pass the Verifier name here
                typeOfLogin: 'google', // Pass on the login provider of the verifier you've created
                clientId:
                  '2108.......4gp.apps.googleusercontent.com', // Pass on the Google `Client ID` here
              },
})
9

@vjgee @yashovardhan

I hope this message finds you well. I would like to clarify our current situation and the assistance we need.

Originally, we have been attempting to connect to a private blockchain that requires authentication. As far as we understand, the reference materials you have provided pertain to the authentication mechanism on the web3auth side.

What we aim to do, however, is to connect to a private blockchain that requires its own authentication. Would there be a way to incorporate the authentication details of this private chain into the connection process? Does web3auth support a feature where we can embed authentication information to connect to such a private chain?

We appreciate your time and assistance on this matter. Looking forward to hearing from you soon.

10

@fc.kikkawa Please try using the CHAIN_NAMESPACES.OTHER in chainNamespace field. And use the CommonKeyProvider from this and pass the privateKeyProvider you get to OpenLoginAdapter, also shown in the given docs link.

11

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