API for client cert

[zhaohuabing]

Related: #2536

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 64.49%. Comparing base (29946b0) to head (c54cc08).
Report is 68 commits behind head on main.

❗ Current head c54cc08 differs from pull request most recent head e4b4ac4. Consider uploading reports for the commit e4b4ac4 to get more accurate results

Additional details and impacted files

@@            Coverage Diff             @@
##             main    #2984      +/-   ##
==========================================
- Coverage   66.51%   64.49%   -2.02%     
==========================================
  Files         161      121      -40     
  Lines       22673    21388    -1285     
==========================================
- Hits        15080    13794    -1286     
- Misses       6720     6723       +3     
+ Partials      873      871       -2     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

[guydc]

LGTM! As we also have an assignee for #2901 , it would be great to get this API in.

[arkodg]

should we call this ClientTLS ?

[zhaohuabing]

@guydc mentioned he wants to add some server-side settings later. If that's the case, then it would be better to use a more generalized name.

[guydc]

Hi @zhaohuabing ! Did you see this #3218? It also covers the API/Impl for client cert based on previous discussion in the community meeting.

[zhaohuabing]

Hi @zhaohuabing ! Did you see this #3218? It also covers the API/Impl for client cert based on previous discussion in the community meeting.

Let's do it in #3218 since my focus is now on wasm and filter ordering.