16.01.2013 Views

Microsoft Sharepoint Products and Technologies Resource Kit eBook

Microsoft Sharepoint Products and Technologies Resource Kit eBook

Microsoft Sharepoint Products and Technologies Resource Kit eBook

SHOW MORE
SHOW LESS

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

740 Part VIII: Securing SharePoint <strong>Products</strong> <strong>and</strong> <strong>Technologies</strong><br />

6. If one or more Inheritance Overrides dialog boxes appear, click Select All,<br />

<strong>and</strong> then click OK for each dialog box.<br />

Note You can map client certificates to Windows security accounts <strong>and</strong><br />

then use client certificates for authentication. This process is called an<br />

account mapping. You enable account mapping by selecting Enable client<br />

certificate mapping check box from the Secure Communications dialog.<br />

For more information <strong>and</strong> detailed instructions, refer to the white paper<br />

“Enabling Client Certificates <strong>and</strong> Using Client Certificates When Crawling<br />

Content with SharePoint Portal Server 2003,” located at http:<br />

//www.microsoft.com/technet/prodtechnol/office/sps2003/maintain<br />

/clicerts.asp?frame=true.<br />

To create a certificate trust list (optional)<br />

This step is optional. After you have required client certificates, you can further<br />

tighten the access security by specifying the list of certificate authorities (CAs) that<br />

your portal site trusts. A client with a certificate issued by a CA that is a member of<br />

this list will be allowed access, whereas clients with certificates issued by other CAs<br />

will be denied access to your portal site.<br />

Before you can add the certificate authorities to a certificate trust list, the certificate<br />

authorities must be installed on the server. The steps for installing the certificate<br />

authorities on the server are found in “Obtaining <strong>and</strong> Installing the Certificate<br />

Authority Root” in the “Troubleshooting” section at the end of this chapter.<br />

Both the CA that issued the client certificate <strong>and</strong> the CA that issued the server<br />

certificate must be considered trusted certification authorities. If the server certificates<br />

<strong>and</strong> client certificates are issued by the same certification authority <strong>and</strong> you<br />

successfully performed certification validation in the procedure “To verify that the<br />

certificate is valid” earlier in this chapter, the CA is installed on the server.<br />

To check if the CA is installed on the server, you may do the following:<br />

1. Obtain the client certificate without a private key (.cer file). The client certificate<br />

without the private key can be exported from the computer where the certificate<br />

is installed.<br />

2. Right-click the .cer file, point to Open With, <strong>and</strong> then click Crypto Shell<br />

Extensions.

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!