lighthouse-pulse/testing/web3signer_tests/tls
Peter Davies 807283538f Add client authentication to Web3Signer validators (#3170)
## Issue Addressed

Web3Signer validators do not support client authentication. This means the `--tls-known-clients-file` option on Web3Signer can't be used with Lighthouse.

## Proposed Changes

Add two new fields to Web3Signer validators, `client_identity_path` and `client_identity_password`, which specify the path and password for a PKCS12 file containing a certificate and private key. If `client_identity_path` is present, use the certificate for SSL client authentication.

## Additional Info

I am successfully validating on Prater using client authentication with Web3Signer and client authentication.
2022-05-18 23:14:37 +00:00
..
lighthouse Add client authentication to Web3Signer validators (#3170) 2022-05-18 23:14:37 +00:00
web3signer Add client authentication to Web3Signer validators (#3170) 2022-05-18 23:14:37 +00:00
generate.sh Add client authentication to Web3Signer validators (#3170) 2022-05-18 23:14:37 +00:00
README.md Web3Signer support for VC (#2522) 2021-09-16 03:26:33 +00:00

TLS Testing Files

The files in this directory are used for testing TLS with web3signer. We store them in this repository since the are not sensitive and it's simpler than regenerating them for each test.

The files were generated using the ./generate.sh script.