MessageSecurityOverMsmqElement.ClientCredentialType Property

public:
 property System::ServiceModel::MessageCredentialType ClientCredentialType { System::ServiceModel::MessageCredentialType get(); void set(System::ServiceModel::MessageCredentialType value); };

[System.Configuration.ConfigurationProperty("clientCredentialType", DefaultValue=System.ServiceModel.MessageCredentialType.Windows)]
public System.ServiceModel.MessageCredentialType ClientCredentialType { get; set; }

[<System.Configuration.ConfigurationProperty("clientCredentialType", DefaultValue=System.ServiceModel.MessageCredentialType.Windows)>]
member this.ClientCredentialType : System.ServiceModel.MessageCredentialType with get, set

Public Property ClientCredentialType As MessageCredentialType

Property Value

The MessageCredentialType security setting for messages sent over the MSMQ transport.

Attributes

ConfigurationPropertyAttribute

Remarks

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 ClientCredentials class.

  Note

  WCF does not support sending a password digest or deriving keys using password and using such keys for message security. As such, WCF 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 ClientCredentials class or ClientCredentials behavior. The service credential in this case needs to be specified using the ClientCredentials class or ClientCredentials behavior by specifying the serviceCertificate.

• CardSpace: This allows the service to require that the client be authenticated using a CardSpace. The ServiceCertificate 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.