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
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
The text was updated successfully, but these errors were encountered:
songhaideng
changed the title
tlsInitiator set pfx file,then client.SendAsync(), a sspi error has occurred.
TLS: tlsInitiator set pfx file,then client.SendAsync(), a sspi error has occurred.
Nov 29, 2023
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.
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
The text was updated successfully, but these errors were encountered: