fix: make intermediates work with 'select-client-certificate' #29552
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description of Change
Fixes #28553.
cc @zcbenz @deepak1556
No test added because I wasn't sure there's a viable way to make one (no current tests for this functionality) since it pulls client certificates from the system store. See #21980.
Manually reproduced and tested the fix. The fix is straight forward, but if anyone else really feels like confirming it themselves, these are the steps I used on macOS, it was a bit of a pain:
Keychain Access
, useKeychain Access -> Certificate Assistant
to create a certificate chain, using 'SSL Client' for the type for all certificates. Create:SSL_CLIENT_CERT_CHAIN_1
field is populated if the chain was sent to the server.Chromium Patch for Manual Testing (macOS)
Checklist
npm test
passesRelease Notes
Notes: Fixed sending intermediate certificates with 'select-client-certificate' event callback