Page 1 of 1
SelectClientCertificate is no longer triggered
Posted: Tue Nov 02, 2021 12:44 pm
by Farderlorn
Since the last two updates,
"SelectClientCertificate" is no longer triggered.
Programs that were compiled with an earlier version still call the event.
Can anyone confirm this?
Is it a bug or did the behaviour change since the last versions?
Re: SelectClientCertificate is no longer triggered
Posted: Wed Nov 03, 2021 8:32 am
by salvadordf
Hi,
I tested a Spanish government website, that event was triggered as always and I could select my certificate.
I used the latest CEF binaries for this test.
Can you provide more details about this issue?
Can you check the validity of the certificates?
Have you tested this with the latest Chrome/Chromium version?
Re: SelectClientCertificate is no longer triggered
Posted: Wed Nov 03, 2021 10:11 am
by Farderlorn
Hi,
it was a false positive, sorry.
I was just too stupid to notice that the tested URLs were no longer correct.
I guess I played around with the URLs in an earlier test (weeks ago).
As soon as you do it right - it works
Thank you for the quick answer and help.
Re: SelectClientCertificate is no longer triggered
Posted: Fri Nov 05, 2021 5:09 pm
by Farderlorn
Apparently, there is a problem, but in cef_binary newer than 89
I was able to trigger the error again, if the URL was not unique but triggered a redirect.
The correct URL would be "https://www.haftpflichtkasse.de/extranet/secure/auth?do=lg_login"
and "https://www.haftpflichtkasse.de/extranet" produces "-110=ERR_SSL_CLIENT_AUTH_CERT_NEEDED"
(right clicking and selecting 'Back' leads to the login dialog)
Other browsers show the certification dialog directly
The problem is discussed here:
SSL_CLIENT_AUTH_CERT_NEEDED after redirect to different port
https://www.magpcss.org/ceforum/viewtopic.php?t=18437
more
https://bitbucket.org/chromiumembedded/cef/issues/3204/cef-builds-newer-than-89-fail-with
Re: SelectClientCertificate is no longer triggered
Posted: Fri Nov 05, 2021 5:47 pm
by salvadordf
Try setting GlobalCEFApp.DisableRequestHandlingForTesting to TRUE before the GlobalCEFApp.StartMainProcess call in the DPR file.
That property is equivalent to the workaround given in the CEF issue report.