Firebase locally

[irux]

Hello, I am trying to log in with firebase locally with the emulator as this guide show you, but I am getting a 404 when I try to use the method connectTo

here the response:

{
  "success": false,
  "message": "Invalid public key"
}

does someone have experience with this ?

[irux]

I am looking more deeply to the problem and I think the problem is that the emulator doesn't sign the jwt tokens. That means when I give the jwk endpoint of the guide, it will fail because the tokens are not signed. I can theoretically write an endpoint with empty keys that would accept this token, right ?

I tried something like this as JWKS https://laprop-test.s3.filebase.com/test.json but it didn't work. Do the library support hs256 ?

[irux]

I tried something more simple... this:

const initWeb3Wallet = async () => {


  const clientId = 'MYID';
  const web3auth = new Web3Auth({
    clientId,
    chainConfig: { // this is ethereum chain config, change if other chain(Solana, Polygon)
      chainNamespace: CHAIN_NAMESPACES.EIP155,
      rpcTarget: 'https://mainnet.infura.io/v3/776218ac4734478c90191dde8cae483c',
    },
  });
  await Promise.resolve();
  await web3auth.initModal();
}

and I get this:

[rinzler99]

Hey @irux , I am assuming that you are using custom authentication. For custom auth you should use web3authCore sdk not web3auth sdk. As I can see in your code your are using web3auth sdk. Please refer to below code when you want to use custom auth.

import { Web3AuthCore } from "@web3auth/core";
import { CHAIN_NAMESPACES } from "@web3auth/base";

const web3auth = new Web3AuthCore({
  chainConfig: {
    clientId: "YOUR_WEB3AUTH_CLIENT_ID",
    chainNamespace: CHAIN_NAMESPACES.EIP155, // SOLANA, OTHER
    chainId: "0x1",
  },
});
await web3auth.init();

[irux]

Unfortunately with both I get this #630 (reply in thread)

[rinzler99]

ohh, can you share your code snippet for web3authcore configuration, as web3authCore requires openlogin adapter too I wanna take a look at it.

[himanshuchawla009]

@irux , You can ignore that 404 error, Is it blocking your login flow? The purpose of that call is to validate the user session and to do that we create a random session priv key on the frontend and send the corresponding pub key to backend to check if session exist, it returns 404 always if session doesn't exists on the first call but it should not block your login flow and also we don't support hs256 keys for jwts

[irux]

btw @himanshuchawla009 I am using hs256 for my test environment and it works great! fyi! :)

[bolisteward]

hello @irux please can you explain it. Because I'm getting similar error about WalletLoginError: Failed to connect with wallet. Failed to login with openlogin.

[irux]

hello @irux please can you explain it. Because I'm getting similar error about WalletLoginError: Failed to connect with wallet. Failed to login with openlogin.

Hey @bolisteward what is the problem you are having? Are you using Vue framework as me? Do you have some code?

[masehdh]

@irux Hey, I'm trying to implement your solution except with flutter and firebase emulator.
I have a jwks endpoint that is identical to yours.

I also have a custom verifier that points to that jwks endpoint and that checks for the aud claim only.

I sign the unsigned firebase token with the dart_jsonwebtoken package using HS256, and when I decode it, it is identical in structure to the token I get when I don't use the emulator. https://pub.dev/packages/dart_jsonwebtoken

But I still get the error that auth shares couldn't be found. Can I ask what exactly your LoginConfigItem looks like, what your extraLoginOptions look like, and what your configuration for your custom verifier is?

[masehdh]

Ended up figuring it out, for others facing a similar issue. https://community.web3auth.io/t/firebase-local-emulator-does-not-work/3650/4