Workflow Manager Fail with “Trusted provider is missing” error

I encountered this problem with a customer where one of our workflow heavy applications stopped to function .

The error I got within ULS Logs look like

00000003-0000-0ff1-ce00-000000000000  trusted provider is missing

Turns out it is a security change to the IIS Application for the “Workflow Management Site” where the Authentication provider included

Asp.Net Impersonation Enabled 
Along with other changes to that IIS application .


This customer is using SharePoint 2013 Enterprise on premises with NTLM only in a windows integrated mode , no SSL .

After narrowing down the issue to “Authentication problem” I did setup a new WFM with OOB configuration.

Asp.Net Impersonation Disabled 

I have checked all those settings below this will fix this issue after you restart the application pool.

See Below

Best of Luck.







Claims Based Authentication

Claims based authentication is not a new concept , but it was recently adopted by Microsoft and other major software giants as a standard.

The main purpose and use of the CBA , is authentication against cloud services and also to be used with Federated Identity services.

Some core concepts include

STS : Security Token Service .

RP : Relying Party



Issuing Authority

  1. Also read more on the WIF ( Windows Identy Foundation ) that is part of .NET 3.5 and 4.0
  2. Also read more on the Geneva Project ( later changed to ADFS 2.0 ) Active Directory Federation Services , if you plan to use your own AD as an account /Identity silo .

That would open up a whole world of

[1] How can I Use my Cloud application , yet use my local AD to do authetication.

[2] how can I extend my application to use open Identiy providers like ( Google ID , Live ID , Amazon ws , Yahoo ID etc. )

I was concerned about how to make this work with the new SharePoint 2010 directly , I noticed that out of the box , no Identiy Provider list to choose from (silly me).  from which I started finding out more about this whole project.

I came across this blog during my researh and I believe it is the most detailed.

It is by Steve Peschka, (great job  Steve)

Hope that puts you on the right track.

Best of Luck