ADFS Passive Request = "There are no registered protocol handlers"

Solution 1:

Finally found the solution after a week of google, tries, server rebuilds etc!

(This guru answered it in a blink and no one knew it! https://www.experts-exchange.com/questions/28994182/ADFS-Passive-Request-There-are-no-registered-protocol-handlers.html)

The IdP-Initiated SSO page (https://fs.t1.testdom/adfs/ls/idpinitiatedsignon.aspx). Note that if you are using Server 2016, this endpoint is disabled by default and you need to enable it first via the AD FS console or

Set-AdfsProperties -EnableIdPInitiatedSignonPage $true

--

My question is, if this endpoint is disabled, why isnt it listed in the endpoints section of ADFS Management console as such?!! It said enabled all along all this time over there. And this painful untraceable error msg in the log that doesnt make any sense! All windows does is create logs and logs and logs and yet this is the error log we get!

Solution 2:

1.If you want to check if ADFS is operational or not, you should access to the IDPInitiatedSignon page with URL: https://<ADFSExternalDNSName>/adfs/ls/IdpInitiatedSignon.aspx

as well as the metadata page with URL: https://<ADFSExternalDNSName>/federationmetadata/2007-06/federationmetadata.xml

More details about this could be found here.

2.That's not recommended to use the host name as the federation service name. A correct way is to create a DNS host(A) record as the federation service name, for example use sts.t1.testdom in your case.