Part 5b: Windows Server 2012 R2 AD FS - Federated Web SSO

  • Article

This is Part 5b of a multi-part series on how to deploy a complete end-to-end Federated Web SSO solution using Windows Server 2012 R2's AD FS role and the Web Application Proxy. In this part I will deploy FABRIKAM's highly available Federation Service. This part is a continuation of part 5a where CONTOSO's federation services were deployed. FABRIKAM's federation services will now be deployed.

In case you missed it:

Here is Part 1 - Overview

Here is Part 2 - Installing AD DS, AD CS, and DNS Records

Here is Part 3 - Installing SQL Database Services

Here is Part 4a - Installing CONTOSO's SharePoint Services

Here is Part 4b - Installing FABRIKAM's SharePoint Services

Here is Part 5a - Installing CONTOSO's AD FS Services

Topology

The following topology highlights in yellow the two servers that will be built for parts 5a and 5b and where they fit into the overall topology. If you wish to see the full topology click here

 

Deploy FABRIKAM's Federation Servers

The following sections will deploy FABRIKAM's federation servers in a highly available configuration. 

Deploy FABRIKAM's First Federation Server

  1. Log into the FABRIKAM domain controller (FABR-DC01) and create a new Domain User called srv_ADFS
  2. If you have not already done so, create a new DNS A record called sts.fabrikam.com with an IP address of 192.168.30.25 which is the network loadbalanced virtual IP address for the federation service.
  3. Log into the FABRIKAM SQL server (FABR-SQ01) and give srv_ADFS sysadmin rights.
    1. Open SQL Server Management studio > Security > Logins > New Login > Search > Locations > Entire Directory > OK
    2. Enter srv_adfs then press Enter
    3. Select Server Roles > Check sysadmin > OK
    4. In a production environment the rights should be modified to give the service account the least permissions necessary after AD FS is deployed.
  4. Deploy a Windows Server 2012 R2 workgroup server and configure the IP addess, subnet mask, hostname, and DNS servers. For the purposes of this series the information will be as follows:
    1. Hostname: FABR-FS01
    2. IP Address: 192.168.30.23
    3. Subnet Mask: 255.255.255.0
    4. DNS Servers: 192.168.30.20
  5. Join the fabrikam.com domain
  6. After rebooting, log into the server using FABRIKAM domain credentials (i.e. FABRIKAM\Administrator)
  7. Add AD FS to the server by typing the following command from an elevated PowerShell window: Add-WindowsFeature ADFS-Federation -Includemanagementtools
  8. Request 3 certificates (Service Communications, Decryption, Signing)
    1. From the Start Menu type MMC > File > Add/Remove Snapin > Certificates > Add > Computer Account
    2. Click Next > Finish > OK
    3. Expand Certificates > Right Click Personal > All Tasks > Request New Certificate
    4. Click Next, ensure Active Directory Enrollment Policy is highlighted > Next
    5. Select Web Server then click the More Information is required link
    6. For the subject name select Common Name then type sts.fabrikam.com and click Add
    7. Click the General tab and enter sts.fabrikam.com for the Friendly name and Description
    8. Click the Private Key tab
    9. Select Make private key exportable then click OK > Enroll
    10. Repeat steps 7a-7i to obtain 2 more certs with a subject name of sts-dec.fabrikam.com and sts-sig.fabrikam.com
  9. The service communications certificate should have a subject name of sts.fabrikam.com, the decryption certificate should have a subject name of sts-dec.fabrikam.com, and the signing certificate should have a subject name of sts-sig.fabrikam.com
  10. Export all of the certificates to a PFX file before continuing.
    1. Highlight all 3 certificates > Right Click > All Tasks > Export
    2. Click Next > Yes, export the private key > Next > Personal Information Exchange > Next
    3. Select Password and enter a password then click Next
    4. Select a place to save the file > Next > Finish > OK
  11. Go back to the certificate management console and give the srv_ADFS service account rights to read the private keys
    1. Highlight a Certificate > Right Click > All Tasks > Manage Private Keys > Add > srv_ADFS > Uncheck Full Control
    2. Click OK
    3. Repeat for all 3 certificates
  12. Open an elevated PowerShell window and type the following command: dir cert:localmachine\my
  13. Open Notepad and copy and paste the thumbprints from each certificate to the proper locations within the following command after typing the following PowerShell command into the Notepad document:
    1. $fsCred = Get-Credential
    2. Install-AdfsFarm -CertificateThumbprint <thumbprint> -DecryptionCertificateThumbprint <thumbprint> -SigningCertificateThumbprint <thumbprint> -FederationServiceName sts.fabrikam.com -SQLConnectionString "Data Source=FABR-SQ01;Integrated Security=True" -ServiceAccountCredential $fsCred -FederationServiceDisplayName "FABRIKAM Users"
    3. The completed command should look similar to the one shown in the following Figure.
  14. Copy the completed PowerShell commands from Notepad to an elevated PowerShell window. Enter FABRIKAM\srv_ADFS and the password for srv_ADFS when prompted then press Enter to continue
  15. You should get a message stating that the deployment was successful.
  16. Type the following PowerShell command to verify that the service successfully installed: Test-AdfsFarmInstallation -FederationServiceName sts.fabrikam.com then enter the credentials for FABRIKAM\srv_ADFS when prompted. Your output should be similar to the one shown in the following Figure.

Deploy FABRIKAM's Second Federation Server

  1. Deploy a Windows Server 2012 R2 workgroup server and configure the IP addess, subnet mask, hostname, and DNS servers. For the purposes of this series the information will be as follows:
    1. Hostname: FABR-FS02
    2. IP Address: 192.168.30.24
    3. Subnet Mask: 255.255.255.0
    4. DNS Servers: 192.168.30.20
  2. Join the fabrikam.com domain
  3. After rebooting, log into the server using FABRIKAM domain credentials (i.e. FABRIKAM\Administrator)
  4. Add AD FS to the server by typing the following command from an elevated PowerShell window: Add-WindowsFeature ADFS-Federation -Includemanagementtools
  5. Copy the private keys that were exported from FABR-FS01 to FABR-FS02
  6. Import the private keys to FABR-FS02
    1. Double click the PFX file and select LocalMachine then click Next > Next
    2. Enter the password that you entered when you exported the private keys then click Next
    3. Select Place all certificates in the following store > Browse > Personal > OK > Next > Finish > OK. Note: As a best practice you should delete the PFX file once the certificates have been imported into the certificate store.
  7. Open the certificate management console and give the srv_ADFS service account rights to read the private keys
    1. Highlight a Certificate > Right Click > All Tasks > Manage Private Keys > Add > srv_ADFS > Uncheck Full Control
    2. Click OK
    3. Repeat for all 3 certificates
  8. Open an elevated PowerShell window and type the following command: dir cert:localmachine\my
  9. Open Notepad and copy and paste the service communications thumbprint (subject: sts.fabrikam.com) cto the proper location within the following command after typing the following PowerShell command into the Notepad
    1. $fsCred = Get-Credential
    2. Add-AdfsFarmNode -ServiceAccountCredential $fsCred -SQLConnectionString "Data Source=FABR-SQ01;Integrated Security=True" -CertificateThumbprint "<thumbprint>"
  10. The completed command should look similar to the one shown in the following Figure.
  11. You should get a message stating that the deployment was successful.
  12. Type the following PowerShell command to verify that the service successfully installed: Test-AdfsFarmInstallation -FederationServiceName sts.fabrikam.com then enter the credentials for FABRIKAM\srv_ADFS when prompted. Your output should be similar to the one shown in the following Figure.

Install Windows NLB (OPTIONAL)

The following steps will make the AD FS deployment a highly available service. Typically in a production environment, a 3rd party load balancer is used to provide this functionality. If you choose to skip the deployment of Windows NLB or a 3rd party load balancer ensure to change the sts.fabrikam.com DNS A record IP address to point to either FABR-FS01 or FABR-FS02.

Deploy NLB to FABR-FS01

  1. Log into FABR-FS01 and open an elevated PowerShell window
  2.  Type the following commands to add NLB to CONT-FS01 and to configure the port rules
    1. Add-WindowsFeature NLB,RSAT-NLB -IncludeManagementTools
    2. New-NlbCluster -Hostname FABR-FS01 -Interface "Ethernet" -ClusterName ADFSNLB -ClusterPrimaryIP 192.168.30.25 -SubnetMask 255.255.255.0 -OperationMode Multicast. Note: if you are unsure of the Inteface name or this command fails type Get-NetAdapter | fl name to get the interface name
    3. Get-NlbClusterPortRule | Remove-NlbClusterPortRule -Force
    4. Add-NlbClusterPortRule -StartPort 443 -EndPort 443 -IP 192.168.30.25 -Protocol Tcp -Affinity Single -Interface "Ethernet"
    5. Add-NlbClusterPortRule -StartPort 49443 -EndPort 49443 -IP 192.168.30.25 -Protocol Tcp -Affinity Single -Interface "Ethernet"
    6. Verify that the cluster is operational by typing the following command: Get-NlbCluster

Deploy NLB to FABR-FS01

  1. Log into FABR-FS02 and open an elevated PowerShell window
  2. Type the following commands to add NLB to FABR-FS02
    1. Add-WindowsFeature NLB,RSAT-NLB -IncludeManagementTools
    2. Add-NlbClusterNode -NewNodeName FABR-FS02 -NewNodeInterface "Ethernet" -Hostname FABR-FS01 -Interface "Ethernet"
    3. Verify that the cluster is fully converged by typing the following command: Get-NlbCluster

Verify NLB and AD FS Federation Metadata

Verify NLB is fully configured by going to the start screen > type network load balancing manager then press enter. NLB should be similar to the one shown in the following Figure.

Verify AD FS by typing the following URL into a browser window: https://sts.fabrikam.com/FederationMetadata/2007-06/FederationMetadata.xml

You should be presented with a federation metadata page similar to one of the ones shown below depending on your browser's trusted sites and compatibility mode configuration.

If you chose to deploy NLB or a 3rd party loadbalancer, ensure both nodes work as intended before proceeding by drainstopping one of the nodes (Powershell: Stop-NlbClusterNode -Drain -Hostname FABR-FS01 or FABR-FS02). A common problem I have seen when dealing with clustering is that only one node works so users get intermittent errors that can be hard to troubleshoot since traffic occasionally hits the non-working node.

If your environment is virtual and your hypervisor host is Hyper-V and the NLB VIP is unreachable outside of the NLB cluster's VLAN or you encounter intermittent connectivity problems to the VIP then try enabling MAC spoofing for the VM as explained here. If your hypervisor is VMware, you may need a static mapped mac address entry to resolve the issue.

Verify Service Principal Name

Although the AD FS service automatically configures the SPN for the AD FS service account, I always like to verify that it is correct before proceeding. This will also ensure that another account does not have the same SPN which will prevent Kerberos from working. The following steps will verify the SPN.

  1. Log into a FABRIKAM member server.
  2. Open a command prompt and type the following commands
    1. setspn -X
    2. setspn -L srv_adfs
  3. The resulting output should be similar to the output shown in the following Figure. Any duplicates should be resolved before continuing.

Wrap-Up

You now have two forests one named contoso.com and one named fabrikam.com along with the DNS records, certificate services, database services, CONTOSO's and FABRIKAM's SharePoint Foundation 2013 services, and CONTOSO's and FABRIKAM's Windows Server 2012 R2 AD FS services. In the upcoming parts both organization's Web Application Proxies will be deployed and configured to support Federated Web SSO.

 Troubleshooting

  • If you cannot connect to the SQL server and the Windows Firewall is enabled ensure port TCP 1433 is enabled inbound on the Windows Firewall as per the following instructions.
  • If the installation of AD FS fails when connecting to SQL, verify that the service account has at least DB Owner on the SQL server for the target database
  • If you get an error when attempting to obtain a certificate ensure that Domain Computers have rights to read the Web Server template
  • If you get an error when attempting to obtain a certificate ensure thatthe CRL has not expired
  • If you get an error "Install-AdfsFarm: Parameter set cannot be resolved..." verify that the command and all parameters are properly spelled and that all mandatory parameters are present
  • If you get an error stating page cannot be found when viewing https://sts.fabrikam.com/FederationMetadata/2007-06/FederationMetadata.xml verify that the sts.fabrikam.com record was created and points to either the AD FS server IP address or the NLB Virtual IP address (VIP)

Comments

  • Anonymous
    January 01, 2003
    any word on part 6 - Application Proxies and configured to support Federated Web SSO?
  • Anonymous
    September 25, 2014
    Overview
    The purpose of this series is to walk you through step-by-step from start to finish setting
  • Anonymous
    October 19, 2014
    Part 5b: Windows Server 2012 R2 AD FS - Federated Web SSO - PlatformsPFE - Site Home - TechNet Blogs
  • Anonymous
    February 16, 2015
    This is Part 6a of a multi-part series on how to deploy a complete end-to-end Federated Web SSO solution
  • Anonymous
    October 26, 2015
    This is Part 6b of a multi-part series on how to deploy a complete end-to-end Federated Web SSO solution
  • Anonymous
    October 27, 2015
    This is Part 7 of a multi-part series on how to deploy a complete end-to-end Federated Web SSO solution
  • Anonymous
    October 28, 2015
    This is Part 8 of a multi-part series on how to deploy a complete end-to-end Federated Web SSO solution
  • Anonymous
    October 28, 2015
    This is Part 9 of a multi-part series on how to deploy a complete end-to-end Federated Web SSO solution