You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug OnSelectClientCertificate does not work with chrome-runtime. Now that alloy is not supported there isn't any option to enable OnSelectClientCertificate. When using chrome-runtime when visiting an mtls protected URL a certificate selection dialog appears. Previously when using alloy OnSelectClientCertificate would be called.
To Reproduce
Steps to reproduce the behavior:
One Windows install a client certificate in the Windows certificate store
Start cefclient with the --ssl-client-certificate=<certificate subject name> option
Visit a url that requests and mtls certificate.
Chrome will popup a certificate selection dialog.
Expected behavior
OnSelectClientCertificate should be called and the certificate matching the certificate subject name should be used.
Versions (please complete the following information):
OS: Windows 11
CEF Version: 128.4.9
The text was updated successfully, but these errors were encountered:
Does ChromeContentBrowserClientCef just need the SelectClientCertificate implementation from the former AlloyContentBrowserClient or is it more complex than that?
Describe the bug
OnSelectClientCertificate
does not work with chrome-runtime. Now that alloy is not supported there isn't any option to enableOnSelectClientCertificate
. When using chrome-runtime when visiting an mtls protected URL a certificate selection dialog appears. Previously when using alloyOnSelectClientCertificate
would be called.To Reproduce
Steps to reproduce the behavior:
--ssl-client-certificate=<certificate subject name>
optionChrome will popup a certificate selection dialog.
Expected behavior
OnSelectClientCertificate should be called and the certificate matching the certificate subject name should be used.
Versions (please complete the following information):
The text was updated successfully, but these errors were encountered: