Ssl Error Severity Enum
The category of error that occurs on an SSL connection.
public enum class SocketSslErrorSeverity
/// [Windows.Foundation.Metadata.ContractVersion(Windows.Foundation.UniversalApiContract, 65536)] enum SocketSslErrorSeverity
[Windows.Foundation.Metadata.ContractVersion(typeof(Windows.Foundation.UniversalApiContract), 65536)] public enum SocketSslErrorSeverity
var value = Windows.Networking.Sockets.SocketSslErrorSeverity.none
Public Enum SocketSslErrorSeverity
Windows 10 requirements
Windows 10 (introduced in 10.0.10240.0)
Windows.Foundation.UniversalApiContract (introduced in v1.0)
Fatal errors indicate the SSL server’s certificate cannot be validated. Reasons for encountering this severity level include:
Ignorable errors indicate that the SSL server’s certificate cannot be properly validated.
Disregarding Ignorable errors may result in the loss of privacy or integrity of the content passed over the SSL session. Reasons for encountering this severity level include:
No error occurs on the SSL connection.
The SocketSslErrorSeverity enumeration indicates the category of error that occurs when an SSL connection to a server is established.
SSL server errors should only be ignored in advanced scenarios. Disregarding server certificate errors classified as either Ignorable or Fatal may result in the loss of privacy or integrity of the content passed over the SSL session.
Some organizations may use self-signed certificates for private use rather than registered the certificates with a trusted certificate authority. An SSL connection to these sites might be a case where an Ignorable error might be tolerated if the server's SSL certificate can be verified by other means.
To validate self-signed certificates effectively, an app must validate the public key of the certificate (using a certificate thumbprint or hash of the public key, for example). See the Windows.Security.Cryptography.Certificates namespace for classes that support calculating certificate thumbprints and other validation operations.
If the public key cannot be validated, displaying other certificate details to users by default is not advisable. This may cause users to assume the information is valid when it may in fact be provided by an attacker.