Prerequisites for Configuring AD FS with SAML 2.0

  • Two servers, one to host AD FS 2.0 and the other to host Access Manager.

  • AD FS 2.0 is deployed.

  • ADFS 2.0 with WIF is deployed.

    The test deployment that was created in the AD FS 2.0 Federation with a Windows Identity Foundation (WIF) application is used as starting point for this deployment. A single Windows Server 2012 instance (fsweb.contoso.com) is used to host both the AD FS 2.0 federation server and a WIF sample application. It presumes the availability of a Contoso.com domain, in which fsweb.contoso.com is a member server. The same computer can act as the domain controller and federation server in the test deployments.

  • ADFS 2.0 with SharePoint 2010 is deployed.

    The test deployment that was created in Configuring SharePoint 2010 AAM applications with AD FS 2.0 is used as starting point for this deployment. A single Windows Server 2012 instance (fsweb.contoso.com) is used to host the AD FS 2.0 federation server and a Windows Server 2012 instance (SP2010) is used to host the SharePoint 2010 application. It presumes the availability of a Contoso.com domain, in which fsweb.contoso.com is a member server. The same computer can act as the domain controller and federation server in the test deployments.

  • Access Manager is deployed.

    The Access Manager environment in this deployment is hosted by a fictitious company called nam.example.com. Only the Identity Server component of Access Manager is required for this federation. For information about how to install Access Manager, see NetIQ Access Manager 5.0 Installation and Upgrade Guide.