TLS: tlsInitiator set pfx file，then client.SendAsync(), a sspi error has occurred.

[songhaideng]

Expected behavior

tlsInitiator set pfx file，then client.SendAsync(), expect successfully.

Actual behavior

a sspi error has occurred. The received message is abnormal, or the format is incorrect.

Steps to reproduce the behavior

fo-dicom version and OS/platform

5.1.1.0

[songhaideng]

I set X509CertificateCollection to X509Certificate2Collection, then server can verify client Certificate file.

[amoerie]

So, this issue is resolved?

@gofal Should we document somewhere that only X509Certificate2Collection is supported? Or should that work?

[gofal]

With certificates, the main work is not done in code, but before in communication between client and server, which type of certificate to use, do they need to have the same signing authority, what key-size is minimum required etc.
So I would not say, that it's a general documentation that X509Certificate2Collection has to be used. But there may be servers that only support certificates when used with advanced functions as provided in X509Certificate2Collection.
So when updating the documentation, this would be a more general documentation about certificates in .net and not about fo-dicom and how fo-dicom handles certificates.

[songhaideng]

yeah, I use DVTK-DICOM Validatation Tool as Server, Then I can send width Tls Successfully.