I am trying to install ADFS 3.0 on a Server 2012 R2 VM that I've created from the Server 2012 R2 Datacenter VM template on Azure. The server has no other roles on it (and no IIS because ADFS 3.0 does not use IIS), but has ASP.NET 4.5 installed and .NET 4.5. It is fully Windows Updated including the latest 2012 R2 Update that was just released. It is joined to a Server 2012 R2 DC (also an Azure VM running 2012 R2). I've created a self-signed SSL certificate via the domain controller called adfs.azure.xxx.net and installed the root CA and the certificate on the server. I have followed the instructions athttp://goodworkaround.com/node/53.
Following successful installation and configuration (using the Wizard) of the ADFS role, I can go to the pagehttps://adfs.azure.xxx.net/federationmetadata/2007-06/federationmetadata.xml and that works fine, and it brings back a load of xml.
However, when I test the signin page at https://adfs.azure.xxx.net/adfs/ls/ldpinitiatedsignon.aspx on the server, I get a web page come up with the messgae "An error occurred. Contact your administrator for more information." The ADFS Admin log reports the following error:
Encountered error during federation passive request.Additional Data
Protocol Name:
Relying Party:
Exception details:
Microsoft.IdentityServer.RequestFailedException: MSIS7065: There are no registered protocol handlers on path /adfs/ls/ldpinitiatedsignon.aspx to process the incoming request.
at Microsoft.IdentityServer.Web.PassiveProtocolListener.OnGetContext(WrappedHttpListenerContext context)
I have searched all over for this error ('no registered protocol handlers') but cannot find any mention of it anywhere. I've tried this a number of times by creating a new Azure VM server and installing the role after joining the server to the domain, but no success.
I am completely stumped. Can anyone offer any advice?