Using a Custom JWT Auth Provider to get an Ethereum Private Key

[Animalmix55]

Good evening!

I am using Web3Auth and my own backend to generate JWTs to use with a custom verifier. So far, I successfully make it through login, with the popup modal disappearing and connectTo returning a provider, the issue is the final step: getting the private key from the provider.

The following is my code:

const { web3AuthClientId, web3AuthNetwork } = LoginEnvironment;

    const _web3AuthCore = new Web3AuthCore({
        clientId: web3AuthClientId,
        chainConfig: {
            // use defaults
            chainNamespace: CHAIN_NAMESPACES.EIP155,
        },
    });

    const openloginAdapter = new OpenloginAdapter({
        adapterSettings: {
            network,
            clientId,
            uxMode: 'popup',
            loginConfig: (
                Object.keys(FRONTEND_OAUTH_PROVIDERS) as OAuthProvider[]
             ).reduce((all: LoginConfig, cur) => {
                 const provider = FRONTEND_OAUTH_PROVIDERS[cur];
                 const { verifierId } = provider;

                 const config: LoginConfig[string] = {
                     name: cur,
                     verifier: verifierId,
                     typeOfLogin: 'jwt',
                     clientId: 'default', // doesn't matter
                 };

                 return {
                     ...all,
                     [cur]: config,
                 };
             }, {} as LoginConfig),
         },
    });

    _web3AuthCore.configureAdapter(openloginAdapter);

    await _web3AuthCore.init();

    await web3Auth.connectTo(openloginAdapter.name, {
        loginProvider: provider,
        extraLoginOptions: {
            domain: 'DOES NOT MATTER',
            id_token: token,
            verifierIdField: 'userId',
        },
    });

    const web3Provider = web3Auth.provider;
    if (!web3Provider) throw new Error('No provider returned');

    const privateKey = await web3Provider.request({ method: 'eth_privateKey' });
    if (!privateKey) throw new Error('Did not receive private key');

    return String(privateKey);

This works great until the final three lines, where the request throws this console error:

I thought it might be an issue of not specifying a custom RPC but, still, no luck. I used CHAIN_NAMESPACES.OTHER to see if perhaps it was an EVM-specific issue, but then I got this error:

[Animalmix55]

I did some further drilling into the RPC error and discovered this:

Which seems to contradict https://web3auth.io/docs/sdk/web/providers/#examples

[Animalmix55]

Well, I'll be darned, I was using eth_privateKey instead of eth_private_key. I wonder where I got that idea from!