<clientCertificate> of <serviceCredentials>

Defines an X.509 certificate used to sign and encrypt messages to a client form a service in a duplex communication pattern.

<system.serviceModel>

  <behaviors>

    <serviceBehaviors>

      <serviceBehaviors>

        <behavior> of <serviceBehaviors>

          <serviceCredentials> Element

            <clientCertificate> of <serviceCredentials>

                                    
                                    <clientCertificate>
                                
                                    
                                     <certificate/>
                                
                                    
                                     <authentication/>
                                
                                    
                                    </clientCertificate>
                                

Attributes and Elements

The following sections describe attributes, child elements, and parent elements

Attributes

None.

Child Elements

Parent Elements

Remarks

The <certificate> element is used when the service must have the client's certificate in advance to communicate securely with the client. This occurs when using the duplex communication pattern. In the more typical request/response pattern, the client includes its certificate in the request, which the service uses to encrypt and sign its response back to the client. In the duplex communication pattern, however, the service does not have a request from the client and therefore it needs the client's certificate in advance to secure the message to the client. Therefore you must obtain the client's certificate in an out-of-band negotiation, and specify the certificate using this element. For more information about duplex services, see How to: Create a Duplex Contract.

See Also

Reference

X509InitiatorCertificateServiceElement

Other Resources

How to: Create a Duplex Contract
Security Behaviors in Windows Communication Foundation
Working with Certificates

Send comments about this topic to Microsoft.
© Microsoft Corporation. All rights reserved.