System.ServiceModel 4.0.0.0 System.Configuration.ConfigurationElement To be added.

Enables setting message-level security properties on the binding.

Constructor 4.0.0.0 To be added.

Initializes a new instance of the class.

Property 4.0.0.0 System.ComponentModel.TypeConverter(typeof(System.ServiceModel.Configuration.SecurityAlgorithmSuiteConverter)) System.Configuration.ConfigurationProperty("algorithmSuite", DefaultValue=Mono.Cecil.CustomAttributeArgument, Options=System.Configuration.ConfigurationPropertyOptions.None) System.ServiceModel.Security.SecurityAlgorithmSuite To be added. defines a variety of algorithms, such as Canonicalization, Digest, KeyWrap, Signature, Encryption, and KeyDerivation. This property is most relevant when working with a platform that uses a set of algorithms different than the default. You should be aware of the strengths and weaknesses of the relevant algorithms when making modifications to this property.

Specifies the algorithm suite used for security messages at the SOAP level.

Property 4.0.0.0 System.Configuration.ConfigurationProperty("clientCredentialType", DefaultValue=Mono.Cecil.CustomAttributeArgument, Options=System.Configuration.ConfigurationPropertyOptions.None) System.ServiceModel.MessageCredentialType To be added. This property can be set to one of the following values: None: This allows the service to interact with anonymous clients. Neither the service nor the client requires a credential. Windows: This enables the SOAP exchanges to be under the authenticated context of a Windows credential. This always performs Kerberos-based authentication. UserName: This enables the service to require that the client be authenticated using a UserName credential. This credential needs to be specified using class. indigo2 does not support sending a password digest or deriving keys using password and using such keys for message security. As such, indigo2 enforces that the exchange is secured when using UserName credentials. This mode requires that the service certificate be specified on the client side using ClientCredential behavior and serviceCertificate. Certificate: This enables the service to require that the client be authenticated using a certificate. The client credential in this case needs to be specified using the class or ClientCredentials behavior. The service credential in this case needs to be specified using the class or ClientCredentials behavior by specifying the serviceCertificate. CardSpace: This allows the service to require that the client be authenticated using a infocard1. The serviceCertiifcate must be provisioned in the ClientCredential behavior. The Certificate credential for the MessageSecurityOverMsmq is relevant only when the security mode is set to Both or Message.

Gets or sets the security setting for messages sent over the MSMQ transport.

Property 4.0.0.0 System.Configuration.ConfigurationPropertyCollection

To be added.

To be added. To be added.