I gave the demo a try. It does not work out of the box. The issue appears to be with the AD provider hijacking the request.
With AD set to perform auto-login, the call to the digNuke API by the client is 'interrupted' by an NT Authentication Challenge Response. So... I went to digNuke directory and removed the Windows Authentication mechanism. That did get past the first road-block and the client is now able to communicate with the API, but the response for ANY XML-RPC Post call to the ashx receives the HTML response that you receive from a GET on the ashx.
I assume that this is caused by something in DotNetNuke.Authentication.ActiveDirectory and the htmlmodule that is installed via web.config (). I haven't been able to locate the source for this assembly to see what is going on. |