Checklist: Installing a Windows NT token-based application
Applies To: Windows Server 2003 R2
This checklist includes the deployment tasks for preparing an Active Directory Federation Services (ADFS)-enabled Web server running Windows Server 2003 R2, Standard Edition, or Windows Server 2003 R2, Enterprise Edition, for the installation of a Windows NT token–based application.
Important
Make sure that you have set up your ADFS-enabled Web server using the guidance in Checklist: Installing an ADFS-enabled Web server before you proceed with the tasks in this checklist.
Note
Complete the tasks in this checklist in order. When a reference link takes you to a procedure, return to this topic after you complete the steps in that procedure so that you can proceed with the remaining tasks in this checklist.
Checklist: Installing a Windows NT token–based application
Task | Reference | |||
---|---|---|---|---|
Review information in the Active Directory Federation Services Design Guide about the role that ADFS Web Agents play in deploying federated applications. |
||||
Review the information in the Active Directory Federation Services Design Guide to understand important concepts that are relevant to designing and deploying federated Windows NT token–based applications. |
||||
Review information in the Active Directory Federation Services Design Guide to determine whether to use Public Key Infrastructure (PKI) or Service Principal Name (SPN) for the security token protection method. |
||||
Based on the needs of your Windows NT token–based application design, determine whether to use the resource account, resource group, or group-to-UPN (user principal name) impersonation method for purposes of authorization. |
||||
Using Internet Information Services (IIS), configure your Windows NT token–based application to enable anonymous access and to use ASP.NET 2.0. |
||||
Edit the ADFS Web Agent tabs in IIS to enable the Windows NT token–based Web Agent. |
||||
Use the Add Application Wizard in the ADFS snap-in to add a new Windows NT token–based application entry to the Federation Service.
|
Add a new Windows NT token-based application to the Federation Service |
|||
Enable any claims that you want to be sent to the application for authorization purposes. Note Before you begin this task, first install the appropriate claims in the resource partner organization. |
Enable an organization claim for a federated application in the Federation Service |
|||
(Optional) If your application requires them, you can choose authentication method restrictions for your claims-aware application. By default, an application accepts any authentication method that is provided to it. |
Configure authentication methods for a federated application |
|||
(Optional) If your application requires it, you can have the resource federation server sign security tokens using Kerberos or PKI signing schemes. The default token-signing scheme is set to PKI. |
Configure the security token protection method for a federated application |
|||
To ensure the likelihood of successfully tracking down issues that may occur with your Windows NT token–based application, configure event logging. |
Configure event logging for a Windows NT token-based application |
|||
From a client computer, verify that the Windows NT token–based application can be accessed using Integrated Windows authentication, and verify that anonymous access is enabled. |