I had quite some trouble installing and configuring AD FS 3.0 on a Windows Server 2012 R2 with a SQL Server 2005 Standard Edition server to store my Configuration DB in. Therefore I wanted to share that information, hoping it might be useful to others as well.

  1. Prerequisites
  2. Install IIS Role
  3. Configure IIS Default Web Site Binding (Port 443)
  4. Install AD FS Role
  5. Configure AD FS Role
  6. Verify AD FS Role functionality
  7. Troubleshooting AD FS Role

Prerequisites as per Microsoft:

Install Windows Server 2012 R2 IIS Role:

Install IIS 8.5 components required by AD FS with Powershell:

Import-Module ServerManager

Install-WindowsFeature -Name Web-Server, Web-WebServer, Web-Mgmt-Tools

Import appropiate Server Authentication Certificate (aka SSL Certificate) into IIS

The following requirements must be met in order to use the SSL Certificate for AD FS:

  1. Subject name and subject alternative name (SAN) must contain your federation service name, such as adfs.domain.com.
  2. Subject alternative name (SAN) must contain the value enterpriseregistration followed by the UPN suffix of your organization, such as, for example, enterpriseregistration.domain.com.
  1. Open Internet Information Services (IIS) Manager console.
  2. Highlight your Server node.
  3. Click Server Certificates in the middle pane.
    adfs_setup_02
  4. Then click Import in the right Actions pane.
    adfs_setup_03
  5. Browse to your corresponding Server Certificate (must be in pfx file format and thus include a private key), provide the Private Key’s password and click OK.
    adfs_setup_04
  6. The newly imported Server Certificate should now be available for the subsequent https binding.
    adfs_setup_05

Configure https binding for Default Web Site in IIS:

  1. Open Internet Information Services (IIS) Manager console.
  2. Expand your Server node, drill down to your Default Web Site node and highlight it.
  3. Hit Bindings in the right Actions pane:
    iis_bindings_01
  4. Hit Add… in the Site Bindings dialogue:
    iis_bindings_02
  5. Select https in the Type drop down field and your corresponding server certificate in the SSL certificate drop down field. Provide a Host Name, e.g. sso.domain.com or adfs.domain.com (which must be identical to the Server Certificate’s name or part of its SANs). Click OK:
    adfs_setup_06
  6. Close the Site Bindings dialogue window:
    iis_bindings_04
  7. Restart IIS:
    iis_bindings_05

Keep in mind that IIS 8.5 supports Server Name Indication (SNI), i.e. it allows you to install multiple SSL certificates on Microsoft IIS 8.5. In case you missed a certain SAN on the Server Certificate you are now able to add/change FQDNs even afterwards. Check out Federation with ADFS 3.0 and SNI Support for further details.

Install Windows Server 2012 R2 AD FS Role:

Install AD FS Role with Powershell:

Install-WindowsFeature adfs-federation -IncludeManagementTools

adfs_install

Basic configuration of AD FS:

Decide whether you’re going to use Windows Internal Database or a dedicated Microsoft SQL Server to store the AD FS Configuration DB. I chose an existing Microsoft SQL Server 2005 Standard Edition (German Language Setup). And that’s where the trouble began…

  1. Initiate the Active Directory Federation Services Configuration Wizard from within Server Manager:
    adfs_setup_07
  2. Choose whether you want to deploy a new Federation Server Farm or add additional servers to an existing Federation Server Farm and click Next:
    adfs_setup_08
  3. Select an account with appropiate permissions in order to configure the AD FS service and click Next:
    adfs_setup_09
  4. Choose the corresponding SSL Certificate from the drop down list next to SSL Certificate:
    adfs_setup_13
  5. Choose a matching Subject Alternate Name (SAN) from the drop down list next to Federation Service Name:
    adfs_setup_14
  6. Enter your Federation Service Display Name and click Next:
    adfs_setup_15
  7. Review your settings and start configuration by clicking Next:
    adfs_setup_16
  8. After a successful configuration launch the AD FS Management Console:
    adfs_setup_17
  9. During first launch it should look something like this:
    adfs_mmc_01
  10. Basic setup is now complete.

Final configuration tasks with Powershell when using a SQL Server database:

Import-Module ADFS

# Get the credential used for the federation service account
$serviceAccountCredential = Get-Credential -Message “Enter the credential for the Federation Service Account.”

Install-AdfsFarm
-CertificateThumbprint:"769F17D6142B17F831943A9428903C79FD1EF9B9"

-FederationServiceDisplayName:”adfs.domain.com”
-FederationServiceName:"mySSO"

-ServiceAccountCredential:$serviceAccountCredential
-SQLConnectionString:"Data Source=SERV-DB;Initial Catalog=ADFSConfiguration;Integrated Security=True;Min Pool Size=20"

Final configuration tasks with Powershell when using a Windows Internal Database:

Import-Module ADFS

# Get the credential used for the federation service account
$serviceAccountCredential = Get-Credential -Message "Enter the credential for the Federation Service Account."

Install-AdfsFarm
-CertificateThumbprint:”7FC23DC19CB07D33A30965C794FAD96ABD3396D9″
-FederationServiceDisplayName:"mySSO"

-FederationServiceName:”adfs.domain.de”
-ServiceAccountCredential:$serviceAccountCredential

First Time Configuration errors I ran into

#1 Issue: After clicking Finish during the initial Configuration Wizard process I received an error stating "The Certificate specified does not meet all the requirements of an SSL Certificate."

adfs_setup_error_01

#1.1 Problem: Subject alternative name (SAN) value of enterpriseregistration was missing.

#1.1 Solution: Added the Subject alternative name (SAN) value of enterpriseregistration followed by the UPN suffix of my organization, i.e. enterpriseregistration.domain.com

#1.2 Problem: Subject alternative name (SAN) value of enterpriseregistration was included, but certificate was imported using IIS. A subsequent https Binding on the Default Web Site was not possible due to an error A specified logon session does not exist. It may already have been terminated. (Exception from HRESULT: 0x80070520.

#1.2 Solution: Instead of importing the corresponding ADFS certificate via IIS (which can be erronous, obviously), try importing it through MMC by adding the Certificate snap-in for Local Computer; this solved it for me. Have a look at this article: 
Error: "A specified logon session does not exist. It may already have been terminated. (Exception from HRESULT: 0x80070520)" binding SSL certificate using Microsoft IIS 7.0 or 7.5 server

#2 Issue: Upon finishing the initial Configuration Wizard I received a warning "Error occured while writing Windows Firewall rules to allow incoming traffic to the AD FS service."

adfs_setup_error_02

#2 Problem: Windows Firewall service was not running as I already disabled it due to my Best Practice settings for Windows Servers as part of a domain

#2 Solution: I simply checked that AD FS is reachable for incoming traffic on port 443 from within my network as well as from external networks. Keep in mind that your Firewall/Load Balancer/NetScaler settings have to be adjusted accordingly (pls read Prepare your network infrastructure for federation servers as well).

Common issues/errors related to configuring AD FS after installation has been completed successfully

I ran into the following errors post initial configuration:

  • The MSSQL$MICROSOFT##WID service was unable to log on as NT SERVICE\MSSQL$MICROSOFT##WID
  • ADMIN0012: OperationFault
  • ADMIN0017:

Error

The MSSQL$MICROSOFT##WID service was unable to log on as NT SERVICE\MSSQL$MICROSOFT##WID with the currently configured password due to the following error:
Logon failure: the user has not been granted the requested logon type at this computer.

Grant Log on as a Service privilege via GPO to the following users/accounts. Therefore open Default Domain Policy and Default Domain Controller Policy, navigate to Computer Configuration, Policies, Windows Settings, Security Settings, Local Policies, User Rights Assignments. Here edit Log on as a service and add the following groups:

  • IIS_WPG
  • NETWORK
  • NETWORK SERVICE
  • SERVICE

Afterwards run gpupdate /force in an elevated command prompt on the appropiate machine for these changes to take effect.

Change WinSystemLocale with Powershell:

Set-WinSystemLocale en-US

adfs_setlocale

Restart server and verify WinSystemLocale with Powershell:

Get-WinSystemLocale

adfs_getlocale

Check your Event Log under Event Viewer | Applications and Services Logs | AD FS | Admin:

adfs_events

Error Event ID 102:

Log Name:      AD FS/Admin
Source:        AD FS
Event ID:      102
Level:         Error
Keywords:      AD FS
User:          DOMAIN\<DomainAdminAccount>
Computer:      SERV-DC02.domain.local
Description:
There was an error in enabling endpoints of Federation Service. Fix configuration errors using PowerShell cmdlets and restart the Federation Service.

Additional Data
Exception details:
System.ServiceModel.FaultException
1[Microsoft.IdentityServer.Protocols.PolicyStore.OperationFault]: ADMIN0012: OperationFault (Fault Detail is equal to Microsoft.IdentityServer.Protocols.PolicyStore.OperationFault).

adfs_error_102

Error Event ID 220:

Log Name:      AD FS/Admin
Source:        AD FS
Event ID:      220
Level:         Error
Keywords:      AD FS
User:          DOMAIN\<DomainAdminAccount>
Computer:      SERV-DC02.domain.local
Description:
The Federation Service configuration could not be loaded correctly from the AD FS configuration database.

Additional Data
Error:
ADMIN0012: OperationFault

adfs_error_220

After adjusting the corresponding SQL user default language I was able to start the Active Directory Federation Service service:

If you are using SQL as the configuration store you need to check the Default Language of the user connecting to the ADFS SQL configuration DB and be sure that is set to English. ADFS and SQL are both 2012 R2.

adfs_sql_default_language

adfs_service_start_02

Error Event ID 352:

Log Name:      AD FS/Admin
Source:        AD FS
Event ID:      352
Level:         Error
Keywords:      AD FS
User:          DOMAIN\<DomainAdminAccount>
Computer:      SERV-DC02.domain.local
Description:
A SQL operation in the AD FS configuration database with connection string Data Source=np:\\.\pipe\microsoft##wid\tsql\query;Initial Catalog=AdfsConfiguration;Integrated Security=True failed.

Additional Data

Exception details:
A network-related or instance-specific error occurred while establishing a connection to SQL Server. The server was not found or was not accessible. Verify that the instance name is correct and that SQL Server is configured to allow remote connections. (provider: Named Pipes Provider, error: 40 – Could not open a connection to SQL Server)

Connect to your Windows Internal Database (WID) on Windows Server 2012

Follow these steps to connect to the Windows Internal Database on Windows 2012 machine:

  1. Download Microsoft SQL Server 2012 Express from the link
    sql_mgmt_studio_01
    sql_mgmt_studio_02
  2. Install Microsoft SQL Server Management Studio during the Install Wizard on the ADFS server (this is because of the WAP configuration being stored in the ADFS configuration database)
  3. Microsoft SQL Server 2012 Express requires NetFx3 feature (.Net Framework 3.5) to be enabled on the Windows 2012 sever, if you face issue enabling .Net feature follow the steps in the link
  4. Once installation is completed launch SQL Server Management Studio
  5. For server name enter \\.\pipe\MICROSOFT##WID\tsql\query in case you are connecting to a Windows Server 2012 WID:
    sql_mgmt_studio_03
  6. Verify ADFS databases:
    sql_mgmt_studio_04

Verify your AD FS configuration:

Verify whether AD FS Configuration is working properly and whether you can launch the AD FS Management console:

  • Open a browser window, in the address bar type the federation server’s DNS host name, and then append /adfs/fs/federationserverservice.asmx to it for the new federation server, for example:

https://adfs.domain.com/adfs/fs/federationserverservice.asmx

  • If you see the message There is a problem with this website’s security certificate, click Continue to this website. The expected output is a display of XML with the service description document. If this page appears, IIS on the federation server is operational and serving pages successfully (Membership in Administrators, or equivalent, on the local computer is the minimum required to complete this procedure):

adfs_verify_xml

  • Launch the AD FS Mangement console and check for any errors. In case there are not errors upon loading the MMC everything works fine:

adfs_configure_01

Second option to verify whether AD FS is working as expected is to actually login and successfully authenticate against AD FS:

  • Open a browser window, in the address bar type the federation server’s DNS host name, and then append /adfs/ls/IdpInitiatedSignon.aspx to it for the new federation server, for instance:https://adfs.domain.com/adfs/ls/IdpInitiatedSignon.aspx
  • If you see the message There is a problem with this website’s security certificate, click Continue to this website. You will be prompted to enter your credentials:
    adfs_test_01
    adfs_test_02
  • Once you have supplied you credentials and successfully logged on you will see the following page indicating you have been successfully logged in:
    adfs_test_03

For configuration of AD FS 3.0 with Citrix ShareFile and Citrix NetScaler to provide SSO access to Citrix ShareFile with Active Directory credentials, read:

Further reading:

HowTo – Install and Configure Microsoft Active Directory Federation Services 3.0 (ADFS 3.0)
Tagged on:     

One thought on “HowTo – Install and Configure Microsoft Active Directory Federation Services 3.0 (ADFS 3.0)

Leave a Reply