Issues with Edge in the HTTPS handshake process

伟陈 0

In the use of the ARM version of Edge browser, I found that it has a problem in the process of establishing a two-way SSL connection. In the normal two-way SSL handshake process, the server needs to verify the client's certificate information, we use the Microsoft CSP (Cryptographic Service Provider) standard interface to achieve our custom authentication solution in IE and the other version of Edge. However, our custom interface is not called on the ARM version of Edge, resulting in some of our capabilities that cannot be realized, please help solve it.

ShiJieLi-MSFT 10,846 Reputation points Microsoft Vendor

2023-04-24T09:03:39.0233333+00:00

Hi @伟陈,

Would you please provide more information such as any log? By "custom interface", did you mean Microsoft CSP? Also, according to the official document, this API is deprecated. Microsoft may remove this API in future releases.
伟陈 0 Reputation points

2023-06-07T02:19:53.4433333+00:00

Thanks a lot! Maybe I Got it wrong, I'm just wondering how to explain the phenomenon，it doesn't work on the arm version of edge, but works on the other versions of edge, also works on the arm version of chrome(version 114.0.5735.110) in mutual authentication. we find that the arm version of edge doesn't offer client authentication certificates in the HTTPS handshake process. Looking forward to your response。

Share via

Issues with Edge in the HTTPS handshake process

Your answer