Changing the Certificate on ADFS 3.0 and Web Application Proxy (WAP)
As with all systems using certificates for security, there comes a time when the certificate is expiring and needs to be replaced. here’s the procedure for ADFS 3.0 and WAP: Starting with the ADFS server:
- Log onto the ADFS server.
- Add the new certificate to the server. Make sure this is added to the personal certificate store for the computer account. I usually do this using the certificates snap-in in MMC.
- Find the thumbprint for the new certificate. This can be found by looking at the details for the certificate; the thumbprint is usually at/near the bottom of the list of details for the certificate and consists of 40 hexadecimal characters. Take a copy of the thumbprint and ensure that the spaces are removed, so it’s a 40 character string; you’ll need this in a few moments.
- Grant the service account that is running the ‘Active Directory Federation Services’ service read access to the private key. To do this, follow these steps:
- Launch AD FS Management, expand ‘Service’ within the left pane and click ‘Certificates’:
- Click ‘Set Service Communications Certificate…’ from the actions panel at the right of the screen:
- A dialog is shown presenting the available certificates on the server. Select the new certificate that is to be used. If you are unsure of the correct certificate, select each certificate in turn and click the ‘Click here to view certificate properties’ link which is shown and compare the thumbprint with that recorded earlier. Click OK on the dialog once the correct certificate is selected.
- If at this point you restart the server or ADFS service and make a connection to ADFS, you will still be presented with the original certificate. The change in the GUI changes the configuration in the ADFS configuration database, but not the certificate bound to HTTP.sys.
- To complete the configuration change, the following PowerShell command must be run: Set-AdfsSslCertificate –Thumbprint 00112233445566778899aabbccddeeff00112233 Where 00112233445566778899aabbccddeeff00112233 should be replaced with the thumbprint you found earlier.
- Restart the server, or the ADFS service on the server to complete the configuration change.
Additional configuration is required on the WAP server:
- Log onto the WAP server.
- Add the new certificate to the server. Make sure this is added to the personal certificate store for the computer account.
- Run the following PowerShell command to change the certificate: Set-WebApplicationProxySslCedrtificate –Thumbprint 0011223344556677889900aabbccddeeff00112233 Where 00112233445566778899aabbccddeeff00112233 should be replaced with the thumbprint you found earlier.
- All of the publishing rules need to be updated with the thumbprint of the new certificate (you created these originally using PowerShell, right?). This can be done by either deleting the old rules and recreating them with the new certificate thumbprint specified, or the rules can be updated with the new thumbprint, for example: Get-WebApplicationProxyApplication –Name “WebAppPublishingRuleName” | Set-WebApplicationProxyApplication –ExternalCertificateThumbprint “00112233445566778899aabbccddeeff00112233” Where (you guessed it!) 00112233445566778899aabbccddeeff00112233 should be replaced with the thumbprint you found earlier and ‘WebAppPublishingRuleName’ should be replaced with the name of the rule as it is shown in the Remote Access Console. I expected the federation publishing rule that was created automatically when WAP was originally configured to be updated for me, but had to manually switch the certificate on that one.
- Restart the server, or the ADFS and Web Application Proxy services to complete the configuration.
- Test that all of the previously published rules function correctly and provide the new certificate to the computer from which you are making a connection. If you need to check the certificate assigned to a specific publishing rule, the following PowerShell will show all of the properties for the publishing rule: Get-WebApplicationProxyApplication –Name “WebAppPublishingRuleName” | fl Note that the other parameters shown in the list generated by the above can also be changed (with a few exceptions) using the Set-WebApplicationProxyApplication cmdlet.