Skip to content

Ulysses Neves

Microsoft Entra ID, authentication, and hybrid identity troubleshooting.

Menu
  • Início
  • Microsoft Azure
  • Microsoft AD FS
  • Microsoft 365
  • Contact
Menu

AD FS – Fixing error message ‘The SSL certificate specified by thumbprint does not have a subject name that matches the specified’ during WAP trust process

Posted on 29 de October de 2021

Hello guys. Today I will share some guidance on troubleshooting and fixing the error message ‘The SSL certificate specified by thumbprint ‘SSL Thumbprint’ does not have a subject name that matches the specified’ during a WAP trust configuration.

Reason: Before establishing the trust, the Web Application Service does a few pre-validations on the requirements to have the trust correctly established. One of these validations is if the SSL certificate configured with command Set-WebApplicationProxySslCertificate is valid, contains the SAN specified for the federation service and has not been revoked.

In case the correct SAN has not been provided on the SSL certificate or the WAP server is not able to reach the CA which generated the certificate to validate it, your trust will not occur and you might see error messages as below:

On Powershell:

Install-WebApplicationProxy : The SSL certificate specified by thumbprint ‘SSL Thumbprint’ does not have a subject name that matches the specified
Federation Service name: fs.contoso.com
At line:1 char:1

  • Install-WebApplicationProxy -FederationServiceName “fs.contoso.com …
  • ~~~~~~~~~~~~~~~~~
    • CategoryInfo : NotSpecified: (:) [Install-WebApplicationProxy], DisplayableArgumentException
    • FullyQualifiedErrorId : PrerequisiteTest,Microsoft.IdentityServer.Management.Proxy.Commands.InstallProxyCommand

With AD FS Debug log enabled while trying to establish the trust, you might see error message on event ID 12 as below:

Error: Exception: The SSL certificate specified by thumbprint ‘SSL certificate’s thumbprint’ does not have a subject name that matches the specified Federation Service name: fs.contoso.com
StackTrace: at Microsoft.IdentityServer.WebHost.Configuration.Providers.SslCertificateValidationProvider.ValidateSSLCertificate(X509Certificate2 certificate, Boolean usingExistingSSLCert, String parameterName, String federationServiceName)
at Microsoft.IdentityServer.Management.Proxy.Tasks.ResolveSslCertificateTask.ConfigureSslCertificateForPort(IResolveSSLCertificateContext resolveCertContext, String hostName, Int32 httpsPort, String storeName, Boolean acceptClientCerts)
at Microsoft.IdentityServer.Management.Proxy.Tasks.ResolveSslCertificateTask.DoExecution(IDeploymentContext context, IProgressReporter progressReporter)
at Microsoft.IdentityServer.Deployment.Core.Tasks.ConfigurationTaskBase.Execute(IDeploymentContext context, IProgressReporter progressReporter)

Result: Status – Error, Message – An error occurred validating the SSL certificate. The SSL certificate specified by thumbprint ‘SSL certificate’s thumbprint’ does not have a subject name that matches the specified Federation Service name: fs.contoso.com, Context – PrerequisiteTest

Running configuration tasks for Microsoft.IdentityServer.Management.Proxy.Commands.InstallProxyCommand failed.

Checking the SAN on the SSL certificate

As per AD FS requirements, the Certificate contains the federation service name, such as “fs.contoso.com” in the Subject or Subject Alternative Name (SAN). Reference: https://docs.microsoft.com/en-us/windows-server/identity/ad-fs/overview/ad-fs-requirements#ssl-certificates

First, you should confirm if the federation name is covered by the SSL certificate, checking its Subject Alternative Name as below:

Checking if the WAP server is able to validate the certificate

If the SAN is correctly configured, we need to check if the WAP server is able to reach the URL for the Authority Info Access to confirm if this is a valid certificate and its revocations’ information.

To test the connectivity to the service, let’s run the command below using PowerShell:

invoke-webrequest http://status.geotrust.com

Confirmed the lack of connectivity, work with your network team to authorize the WAP server to reach the URL.

After you fix the connectivity issue, run the same command above, and you might see the message below with status code 200, which is successful:

Fixing the WAP trust

Now, with the Web Application server able to validate the SSL certificate, we can establish the trust again running the command below:

$FScredential = Get-Credential
Install-WebApplicationProxy -FederationServiceName "FS01.Contoso.com" -FederationServiceTrustCredential $FScredential -CertificateThumbprint "SSL Certificate's thumbprint"

With the trust configuration succeeded, you might find on AD FS Admin logs event 245 to confirm the successful trust configuration as below:

Summary

In this article, we covered how to troubleshoot and fix the error message ‘The SSL certificate specified by thumbprint ‘SSL Thumbprint’ does not have a subject name that matches the specified’ during a WAP trust configuration.

I hope you have enjoyed reading this article, and it helps you to manage your AD FS environment.

Enjoyed the article? Like and share. 🙂

Note: I do not represent the organization I work for, all the opinions expressed here, are my own. This post is provided AS IS with no warranties or guarantees and confers no rights.

In case you have any suggestions or feedback, please leave a comment.

[ ]’s

Ulysses Neves

Leave a Reply Cancel reply

Your email address will not be published. Required fields are marked *

Recent Posts

  • Microsoft Authenticator Will Block Jailbroken Devices in 2026 — What You Need to Know 17 de March de 2026
  • Enhancing Azure role activation security with FIDO2/Passkeys 23 de September de 2024
  • Microsoft Entra ID CAP | Enforcing WHfB using Authentication Strength 21 de April de 2024
  • Troubleshooting Error Code ‘0x000005e’ in WHfB: PIN Authentication Woes 11 de February de 2024
  • WHfB: Fixing Windows Hello for Business error ‘LogoncertTemplateReady: NO (StateNoTemplate)’ 29 de December de 2023

Archives

  • March 2026
  • September 2024
  • April 2024
  • February 2024
  • December 2023
  • September 2023
  • July 2023
  • June 2023
  • May 2023
  • April 2023
  • March 2023
  • February 2023
  • January 2023
  • December 2022
  • October 2022
  • September 2022
  • August 2022
  • July 2022
  • June 2022
  • May 2022
  • April 2022
  • March 2022
  • February 2022
  • January 2022
  • December 2021
  • November 2021
  • October 2021
  • September 2021
  • August 2021
  • July 2021
  • June 2021
  • May 2021
  • April 2021
  • March 2021
  • February 2021
  • January 2021
  • December 2020
  • November 2020
  • October 2020
  • September 2020
  • August 2020
  • July 2020
  • June 2020
  • May 2020
  • April 2020
  • March 2020
  • February 2020
  • January 2020
  • December 2019
  • November 2019
  • October 2019
  • September 2019
  • August 2019
  • July 2019

Tags

#aaddownleveldevice #aadhybridjoin #adfs #adfsonsql #azuread #azureauth #azureCA #azuredevice #azurehybridjoin #azuremfa #azuresecurity #capolicy #cloudkerberostrust #conditionalaccess #conditionalaccesspolicy #deviceregistration #gmsaaccount #gopasswordless #hybridaadjoin #mfaserver #msadfs #msazure #msidentity #namedlocation #sslcertificatevalidation #tshootadfs #tshoothybridjoin #tshootwaptrust #waptrust #WHFBcerttrust #whfbdeployment #WHfBhybridsetup #widdatabase adconnect authenticationcontext authenticationstrength az500 azuread azuremfa azurepim azuresecurity cloudsecurity microsoft365 msazure WHfB
©2026 Ulysses Neves | Design: Newspaperly WordPress Theme
Ulysses Neves
Gerenciar Consentimento de Cookies
Para fornecer as melhores experiências, usamos tecnologias como cookies para armazenar e/ou acessar informações do dispositivo. O consentimento para essas tecnologias nos permitirá processar dados como comportamento de navegação ou IDs exclusivos neste site. Não consentir ou retirar o consentimento pode afetar negativamente certos recursos e funções.
Funcional Always active
O armazenamento ou acesso técnico é estritamente necessário para a finalidade legítima de permitir a utilização de um serviço específico explicitamente solicitado pelo assinante ou utilizador, ou com a finalidade exclusiva de efetuar a transmissão de uma comunicação através de uma rede de comunicações eletrónicas.
Preferências
O armazenamento ou acesso técnico é necessário para o propósito legítimo de armazenar preferências que não são solicitadas pelo assinante ou usuário.
Estatísticas
O armazenamento ou acesso técnico que é usado exclusivamente para fins estatísticos. O armazenamento técnico ou acesso que é usado exclusivamente para fins estatísticos anônimos. Sem uma intimação, conformidade voluntária por parte de seu provedor de serviços de Internet ou registros adicionais de terceiros, as informações armazenadas ou recuperadas apenas para esse fim geralmente não podem ser usadas para identificá-lo.
Marketing
O armazenamento ou acesso técnico é necessário para criar perfis de usuário para enviar publicidade ou para rastrear o usuário em um site ou em vários sites para fins de marketing semelhantes.
  • Manage options
  • Manage services
  • Manage {vendor_count} vendors
  • Read more about these purposes
Ver preferências
  • {title}
  • {title}
  • {title}