Beacon node is unavailable due to go-eth2-client Package

[xiaowangba2dai]

🎯 Problem to be solved

Hi, when I upgraded charon to the latest v1.0.1 version, I found that the beacon api returned 401.
My beacon-api-endpoint configuration is shown in the following figure (https://ip:port/credential):

The beacon node needs to verify the credentials.

After some analysis, I found that the new version of github.com/attestantio/go-eth2-client will replace the credential with *** , resulting in beacon-api-endpoint can not be used, do you have any solution?

🛠️ Proposed solution

• Approved design doc: link
• Core team consensus on the proposed solution

I hope that the original way of using beacon-api is compatible with the new version.

🧪 Tests

• Tested by new automated unit/integration/smoke tests
• Manually tested on core team/canary/test clusters
• Manually tested on local compose simnet

[KaloyanTanev]

Hi @xiaowangba2dai ! We are aware of this issue with our downstream library of go-eth2-client.
We have recently introduced including beacon node endpoint headers with an extra endpoint charon flag. If your beacon node supports authorization headers, you can use the flag --beacon-node-headers instead of URL path for authz, while we work with attestant team on fixing URL paths. A solution might look like `--beacon-node-headers='Authorization=Basic <AUTH_TOKEN>'" in the example of basic authentication.

[KaloyanTanev]

Closing as it's duplicate of #3228