Professional Documents
Culture Documents
Step-By-Step Guide for AD FS in Windows Server 2008 Errata for Lab Instructions .................. 1 Step 1: Preinstallation Tasks ................................................................................................................ 1 Step 2: Installing AD FS Role Services and Configuring Certificates ............................................ 2 Step 3: Configuring the Web Server.................................................................................................... 2 Step 4: Configuring the Federation Servers ....................................................................................... 2 Running the AD FS Diagnostic Tool.................................................................................................... 2 Additional Configuration for Self-Signed Certificates........................................................................ 5 Step 5: Accessing the Sample Application from the Client Computer ........................................... 6 Other Resources .................................................................................................................................... 9
Step-By-Step Guide for AD FS in Windows Server 2008 Errata for Lab Instructions
This document summarizes issues I encountered while walking through the lab instructions at this site:
http://technet2.microsoft.com/windowsserver2008/en/library/87e1a178-4d8a-4e89-98b0d125f9c84c221033.mspx?mfr=true
After installing AD DS, check your network IP settings again just to make sure the DNS settings are as you set them in the previous step. I found that sometimes the preferred DNS settings were reset.
really helped me to verify certificates were trusted, and that my AD FS configuration was ok. Run this tool and follow the instructions on the blog post. Note the following: You will get warnings on the resource server related to E-mail claims, but those do not cause any concern, just ignore it. If you do get any errors, fix the problems indicated in the error. I only encountered one or two errors related to self-signed certificate trust, which I explain how to fix in the next section.
Here are the screenshots for my steps on the adfsaccount, adfsresource and adfsweb machines:
The private key created for IIS is installed in the Local Machine/My store, called adfsresource.treyresearch.net. Export the public key certificate (.cer) if you havent already and call it adfsresource.cer. o The private key created for the federation server to sign tokens is installed in the Local Machine/My store, called Federation Server adfsresource. Export the public key certificate (.cer) if you havent already and call it adfsresource_ts.cer. Machine: adfsweb o The private key created for IIS is installed in the Local Machine/My store, called adfsweb.treyresearch.net. Export the public key certificate (.cer) if you havent already and call it adfsweb.cer.
Importing certificates, if you havent already: Machine: adfsaccount o Import both adfsaccount.cer and adfsaccount_ts.cer into the Local Machine/Trusted Root Certification Authorities store. Machine: adfsresource o Import adfsresource.cer, adfsresource_ts.cer and adfsaccount.cer into the Local Machine/Trusted Root Certification Authorities store. Machine: adfsweb o Import adfsweb.cer into the Local Machine/Trusted Root Certification Authorities store. Machine: adfsclient o In Step 5 you will be asked to install certificates through the browser. This should work just fine for you, thus no need to manually install to the certificate store. In the event you have issues, or if your client is not Vista o XP, you may need to manually install the certificates to trust the downstream services. o Import adfsaccount.cer, adfsresource.cer and adfsweb.cer into the Local Machine/Trusted Root Certification Authorities store. This tells IE that the web sites can be trusted even though the certificates are self-signed.
Make sure you can ping each machine from the adfsclient machine using not just IP address, but actual DNS check your firewall settings first if you cant, then check your IP/DNS settings on each machine to match Step 1: Ping adfsaccount.adatum.com Ping adfsresource.treyresearch.net Ping adfsweb.treyresearch.net o If DNS is working, you shouldnt have any issues with the steps in this section of the lab. Requiring a Client Certificate: o The second issue I encountered was the client certificate issue. When I browsed to the claims-aware application, IE kept prompting me for a certificate with an empty dialog since I had no certificates. I consulted my friend Joe Kaplan for this, thinking I was missing something in my configuration. We extensively reviewed my setup, and in the process stumbled on the IE settings for Accept certificates. He educated me that the adfs/ls and /adfs/fs directories were already set up properly when you install AD FS on the machinesso I rolled back the step that incorrectly configured each web site for the Accept setting. o If you skipped the step to configure the web sites to require SSL and Accept certificates, you should be able to get through the steps in this section of the lab as well. Section: Configure browser settings to trust the adfsaccount federation server o You should get a certificate error in this step, since the certificate is self-signed. When prompted you can to install the certificate as instructed for the adfsweb site in a later step. Sections: Access the claims-aware application from a Windows XP client/Vista client o Either of these sections should behave similar though instructions to handle self-signed certificates are slightly different. o You may be prompted more than once to install certificates, as you are redirected to the adfsresource and adfsaccount servers. Be prepared to install several certificates.
Appendix A: Creating the Sample Claims-Aware Application The code for default.aspx and default.aspx.cs are fine in this section of the lab. The web.config does not work for IIS7, and this can really throw you for a loop because youll get a generic Internal Server Error at the client machinewith NO IDEA what is behind it. This happened to me and I assumed once again that I had missed a configuration step. Joe Kaplan and I spent a bunch of time trying to trouble shoot my configuration for AD FS on all machines, thinking that was the causeand then he eluded it might be an IIS issue. It turns out that if you browse to the /claimapp from the web server machine you can see the full error. Thanks to my friend Richard Campbell for suggesting I try that one! Since I have custom errors turned off in the web.config, I should have been able to see the error remotelybut apparently something else (perhaps in IIS 7 defaults) is overriding that behavior. Ill have to look into that separately. Here was the full error:
When I was able to see the full error, it pointed to a configuration issue in the web.config related to the HTTP module configuration for the Web Agent (screenshot below). A new section must be added to the web.config, inside the <configuration> element, as follows:
<system.webServer> <modules> <add name="Identity Federation Services Application Authentication Module" type="System.Web.Security.SingleSignOn.WebSsoAuthenticationModul e, System.Web.Security.SingleSignOn, Version=1.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35, Custom=null" preCondition="managedHandler" /> </modules> <validation validateIntegratedModeConfiguration="false" /> </system.webServer>
Other Resources
I used the IE HTTP Headers tool to trace redirects when I started testing the completed lab. This tool is very useful (recommended by Joe): o http://www.blunck.info/iehttpheaders/iehttpheaders.html Joe Kaplan is one of the strongest authorities on AD FS out there today, and he was a tremendous help to me as I got up to speed on the environment. His web site and forum are as follows: o http://www.joekaplan.net o http://directoryprogramming.net ADFS for Developers a nice high level article from Keith Brown on ADFS (for 2003 server): o http://msdn2.microsoft.com/en-us/magazine/cc163520.aspx Understanding WS-Federation to understand the protocols beneath federation, this is helpful: o http://msdn2.microsoft.com/en-us/library/bb498017.aspx