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 – WAP Trust error message System.Security.Cryptography.CryptographicException: Access is denied.

Posted on 21 de August de 2021

Hi mates. Today we’re going to cover the error message System.Security.Cryptography.CryptographicException: Access is denied when configuring the trust between a Web application Proxy and AD FS servers.

How the WAP trust is built

Once you install the WAP service, you need to start a post-install task to establish the trust between the WAP and AD FS servers to have the WAP server act as a reverse proxy to the Relying Parties published on AD FS for users coming from the extranet. During the trust configuration process, you are required to provide an SSL certificate that will be used to establish secure communication to the federation service and a credential with admin permission on the AD FS server. During this process, a self-signed certificate is generated on the WAP server and replicated into the certificate store ADFSTrustedDevices located on the AD FS server using the AD FS service account. This store will contain all self-signed certificates generated by WAP servers that are authorized to request tokens from AD FS backend servers.

If the AD FS service account doesn’t have the appropriate permissions on the store ADFSTrustedDevices, you might face the error messages below when trying to establish the trust:

On PowerShell, you face error message below:

cmdlet Install-WebApplicationProxy at command pipeline position 1
Supply values for the following parameters: FederationServiceTrustCredential
Install-WebApplicationProxy : An error occurred when attempting to establish a trust relationship with the federation service. Error: Internal Server Error

On WAP Debug logs:

Error: Exception: An error occurred when attempting to establish a trust relationship with the federation service. Error: Internal Server Error
StackTrace: at Microsoft.IdentityServer.Management.Proxy.Providers.ProxyTrustProvider.EstablishTrustWithSts(ICredentials credentials, String thumbprint)
at Microsoft.IdentityServer.Deployment.Core.Tasks.ConfigurationTaskBase.Execute(IDeploymentContext context, IProgressReporter progressReporter)
Exception: The remote server returned an error: (500) Internal Server Error.
StackTrace: at System.Net.HttpWebRequest.GetResponse()
at Microsoft.IdentityServer.Management.Proxy.Providers.ProxyTrustProvider.EstablishTrustWithSts(ICredentials credentials, String thumbprint)

Result: Status – Error, Message – An error occurred while attempting to establish a trust relationship with the Federation Server. An error occurred when attempting to establish a trust relationship with the federation service. Error: Internal Server Error, Context – DeploymentTask

On AD FS Admin logs:

The federation server proxy could not establish a trust with the Federation Service.

Additional Data
Exception details: System.Security.Cryptography.CryptographicException: Access is denied.

at System.Security.Cryptography.X509Certificates.X509Store.Add(X509Certificate2 certificate)
at Microsoft.IdentityServer.WebHost.Configuration.Providers.DeviceStoreProvider.AddCertificateToStore(X509Certificate2 certificate)
at Microsoft.IdentityServer.ProxyTrust.ProxyTrustConfigProvider.EstablishProxyTrust(X509Certificate2 trustCertificate)
at Microsoft.IdentityServer.Web.ProxyTrustUserNameListener.OnGetContext(WrappedHttpListenerContext context)

User Action: Ensure that the credentials being used to establish a trust between the federation server proxy and the Federation Service are valid and that the Federation Service can be reached.

On AD FS Debug logs:

Exception: Access is denied.

StackTrace: at System.Security.Cryptography.X509Certificates.X509Store.Add(X509Certificate2 certificate)
at Microsoft.IdentityServer.WebHost.Configuration.Providers.DeviceStoreProvider.AddCertificateToStore(X509Certificate2 certificate)

Identifying the permissions on the ADFSTrustedDevices registry key

By default, the AD FS service account has permissions to write on the certificate store ADFSTrustedDevices. To confirm that, open the Windows Registry on the AD FS server and check if the AD FS service account has write permissions on path: Computer\HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\SystemCertificates\AdfsTrustedDevices

On our case below, to reproduce the issue, I removed the service account’s permissions on the folder.

The scenario below can happen if the AD FS service account is removed by mistake from the folder above, blocking the account to be able to publish the proxy trust certificate generated by the Web Application Proxy servers.

Fixing the permissions on AdfsTrustedDevices’ registry

To fix the issue, add the AD FS service account with write permissions on the folder AdfsTrustedDevices using Windows Registry Editor as below:

Establishing the WAP trust

With the proper permissions set on the AD FS server, we are able to successfully establish the trust:

On WAP server, we confirm the successful trust configuration looking for event 245 on AD FS Admin logs inside Event Viewer:

Summary

In this article, we covered how to troubleshoot the error message System.Security.Cryptography.CryptographicException: Access is denied when configuring the trust between a Web application Proxy and AD FS servers.

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}