'Declaration
 
Public Property LocalCertificateQueries As CertificateQueryCollection

'Usage
 
Dim instance As StaticCertificateSecurityParameters
Dim value As CertificateQueryCollection
 
instance.LocalCertificateQueries = value
 
value = instance.LocalCertificateQueries

public CertificateQueryCollection LocalCertificateQueries {get; set;}

public:
property CertificateQueryCollection^ LocalCertificateQueries {
   CertificateQueryCollection^ get();
   void set (    CertificateQueryCollection^ value);
}

Property Value

The value of this property cannot be null (Nothing in Visual Basic).

The individual elements of the property value cannot be null (Nothing in Visual Basic).

See also: https

Here are some reasons why a collection (and not a single certificate) might be needed:

1. Certificate Chains
   • In many cases, a single certificate is not enough to establish a trust relationship. A certificate chain, which includes intermediate certificates leading up to a root certificate, might be required. The collection allows you to provide the entire chain.
   • Including the root certificate in the collection can help in scenarios where the root certificate is not already trusted by the client or server.
2. Multiple Identities
   • A client might need to present different certificates for different services or endpoints. Having a collection allows the client to choose the appropriate certificate based on the server's request.
   • Some protocols or services might require the client to present multiple certificates for different purposes, such as signing and encryption.
3. Fallback Mechanisms
   • In some cases, a primary certificate might fail or be invalid. Having a collection allows the client to fall back to a secondary certificate without requiring a new connection setup.

Target Platforms: .NET Framework: Windows 10 (selected versions), Windows 11 (selected versions), Windows Server 2016, Windows Server 2022; .NET: Linux, macOS, Microsoft Windows