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 – Troubleshooting error: The certificate specified does not meet all the requirements of an SSL certificate

Posted on 13 de May de 2021

Hi mates. Today we’re going to explain things to check when you receive the error message: The certificate specified does not meet all the requirements of an SSL certificate during a SSL certificate configuration on AD FS.

Scenario: You try to configure the SSL certificate on AD FS or WAP server using commands below:
WAP: Set-WebApplicationProxySslCertificate -Thumbprint ‘<thumbprint of new cert>’
AD FS: Set-AdfsSslCertificate -Thumbprint ‘<thumbprint of new cert>’

Error message:

With AD FS Tracing debug enabled, you identify error message below:

With AD FS Tracing Debug enabled in the WAP, you might be able to find event ID 12 and error messages below:

SetSslCertificate failed for fs.contoso.com:443, CtlStoreName:AdfsTrustedDevices, acceptClientCerts: False

Error: Exception: The certificate specified does not meet all the requirements of an SSL certificate.
StackTrace: at Microsoft.IdentityServer.WebHost.Configuration.Providers.HttpConfiguration.SetSslCertificateSni(String hostName, Int32 port, Byte[] certHashBytes, String defaultSslCtlStoreName, Boolean acceptClientCerts, Boolean force)
at Microsoft.IdentityServer.Management.Proxy.Tasks.UpdateSslCertificateTask.UpdateExistingSslBindings(String thumbprint, String userTlsAuthHostname, Int32 httpsPort)
at Microsoft.IdentityServer.Deployment.Core.Tasks.ConfigurationTaskBase.Execute(IDeploymentContext context, IProgressReporter progressReporter)

Result: Status – Error, Message – An error occurred validating the SSL certificate. The certificate specified does not meet all the requirements of an SSL certificate., Context – PrerequisiteTest

Reason:

The private key on SSL is used to digitally sign the Certificate Signing Request (CSR), and later to secure and verify connections to your server. In case the private key is not imported with the SSL certificate, it cannot be used by AD FS or WAP services. More information on the requirements for SSL certificates, check this Microsoft document.

Checking if the imported certificate has the private key

First requirement to check is if the SSL certificate imported to the server has the private key.

Open the certificate store running certlm.msc on PowerShell and follow steps below:
1 – Expand Personal Certificates
2 – Select the SSL certificate.
3 – Check if you see the message You have a private key that corresponds to this certificate. in the General tab.

In the screen below, we see no private key and we should import the SSL certificate again with the private key.

Exporting the SSL certificate in the AD FS server

If this is the first AD FS server you are configuring with the new SSL certificate, please request the new certificate WITH the private key from the trust CA.

If you are configuring the WAP server and exported the SSL certificate from the AD FS without the private key, follow steps below to export it correctly:

Open the certificate store running certlm.msc on PowerShell and follow steps below:
1 – Expand Personal Certificates
2 – Right click on the SSL certificate.
3 – Select All Tasks.
4 – Select Export…

On the screen below, click Next.

Select Yes, export the private key.

Select the format matching to (.PFX) and click Next.

Type the password to protect the certificate and click Next.

Select a file name to the certificate to be exported and click Next.

Review the configurations and click Finish.

With the export successful, click on OK.

Copy the exported certificate to the WAP server and follow next steps.

Importing the SSL certificate WITH the private key

Before installing and configuring the AD FS role or configuring a new WAP server in the farm, we need to import the SSL certificate WITH the private key. Once you have the certificate, follow steps below:

Run command below to save the password used to protect the certificate into a variable:

$mypwd = Get-Credential -UserName 'Enter password below' -Message 'Enter password below'

Enter the certificate’s password.

Execute the command below to import the certificate in the new server:

Import-PfxCertificate -FilePath C:\temp\cert.pfx -CertStoreLocation Cert:\LocalMachine\My -Password $mypwd.Password

Validating certificate in the store cert:\LocalMachine\My

Make sure SSL certificate was successfully imported into the server running the command below:

Get-ChildItem -Path cert:\LocalMachine\My | FL FriendlyName, Thumbprint, Subject, NotBefore, NotAfter

Check if the certificate imported has teh private key on it.

Configuring the SSL certificate on WAP server

Now that we have the SSL certificate with the private key imported, let’s configure the certificate authentication binding on the WAP using command below:

  Set-WebApplicationProxySslCertificate -Thumbprint 'CERT THUMBPRINT'

You should see in the debug logs event ID 14 for successful SSL certificate installation as below:

Completed running configuration tasks for Microsoft.IdentityServer.Management.Proxy.Commands.SetSslCertificateCommand successfully.

Result: Status – Success, Message – The configuration completed successfully., Context – DeploymentSucceeded

Summary

In this article, we covered how to check the SSL certificate when you receive the error message The certificate specified does not meet all the requirements of an SSL certificate when configuring the SSL certificate on AD FS.

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 suggestion 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}