<authentication> of <serviceCertificate> Element
Specifies the settings used by the client proxy to authenticate service certificates that are obtained using SSL/TLS negotiation.
Schema Hierarchy
<system.serviceModel>
<behaviors>
<endpointBehaviors>
<behavior> of <endpointBehaviors>
<clientCredentials>
<serviceCertificate> of <serviceCredentials>
<authentication> of <serviceCertificate> Element
Syntax
<authentication customCertificateValidatorType="String" certificateValidationMode="None/PeerTrust/ChainTrust/PeerOrChainTrust/Custom"
revocationMode="NoCheck/Online/Offline"
trustedStoreLocation="LocalMachine/CurrentUser" />
Attributes and Elements
The following sections describe attributes, child elements, and parent elements
Attributes
Attribute | Description |
---|---|
customCertificateValidator |
String. A type and assembly used to validate a custom type. |
certifcateValidationMode |
Specifies one of three modes used to validate credentials. If set to Custom, then a customCertificateValidator must also be supplied. The default is ChainTrust. |
revocationMode |
One of the modes used to check for a revoked certificate lists (CRL). The default is Online. |
trustedStoreLocation |
One of the two system store locations: LocalMachine or CurrentUser. This value is used when a service certificate is negotiated to the client. Validation is performed against the Trusted People store in the specified store location. The default is CurrentUser. |
Child Elements
None.
Parent Elements
Element | Description |
---|---|
Specifies a certificate to use when authenticating a service to the client. |
Remarks
The certifcateValidationMode attribute of this configuration element specifies the level of trust used to authenticate certificates. By default, the level is set to ChainTrust, which specifies that each certificate must be found in a hierarchy of certificates ending in a trusted certificate authority at the top of the chain. This is the most secure mode. You can also set the value to PeerOrChainTrust, which specifies that self-issued certificates (peer trust) are accepted as well as certificates that are in a trusted chain. This value is used when developing and debugging clients and services because self-issued certificates need not be purchased from a trusted authority. When deploying a client, use the ChainTrust value instead. You can also set the value to Custom or None. To use the Custom value, you must also set the customCertificateValidator attribute to an assembly and type used to validate the certificate. To create your own custom validator, you must inherit from the abstract X509CertificateValidator class. For more information, see How To: Create a Service Employing a Custom Certificate Validator.
The revocationMode attribute specifies how certificates are checked for revocation. The default is online which indicates that certificates will be checked automatically for revocation. For more information, see Working with Certificates.
Example
The following example does two tasks. It first specifies a service certificate for the client to use when communicating with endpoints whose domain name is www.contoso.com over the HTTP protocol. Second, it specifies the revocation mode and store location used during authentication.
<serviceCertificate>
<defaultCertificate findValue="www.contoso.com"
storeLocation="LocalMachine"
storeName="TrustedPeople"
x509FindType="FindByIssuerDistinguishedName" />
<scopedCertificates>
<add targetUri="https://www.contoso.com"
findValue="www.contoso.com" storeLocation="LocalMachine"
storeName="Root" x509FindType="FindByIssuerName" />
</scopedCertificates>
<authentication revocationMode="Online"
trustedStoreLocation="LocalMachine" />
</serviceCertificate>
See Also
Reference
<authentication> of <clientCertificate> Element
X509RecipientCertificateClientElement
X509CertificateRecipientClientCredential
Authentication
X509ServiceCertificateAuthentication
Other Resources
Security Behaviors in WCF
Working with Certificates
How To: Create a Service Employing a Custom Certificate Validator
Securing Clients
Securing Services and Clients
© 2007 Microsoft Corporation. All rights reserved.
Last Published: 2010-01-05