So, what is the status of the DNN WebAPI (Service Framework) when it comes to using it as a real API in an environment where stuff like Modules and Tabs is not relevant? We notice that if we first login in via the webinterface, our DNN Authentication seem to work fine, but if you just try to authenticate using basic authentication, it doesn't. The Log4Net log is not really talkative about this, even with "All" as log level, but we can see:

2016-09-19 16:56:48,329 [DEVELOPMENT][Thread:42][WARN] DotNetNuke.Entities.Tabs.TabController - Invalid tabId -1 of portal 0
2016-09-19 16:56:48,332 [DEVELOPMENT][Thread:42][WARN] DotNetNuke.Web.Api.StandardTabAndModuleInfoProvider - The specified moniker () is not defined in the system

When we try to authenticate which I can only assume has to do with what's mentioned above about missing tabid and moduleid.

Is it so that unless you have tabid and moduleid, we really shouldn't try to use the DNN WebAPI but instead just use "normal" WebAPI. The main reason we would want to integrate this into DNN WebAPI would be to handle users and permissions in DNN instead of elsewhere, as we already use that for more ordinary Portal stuff.

Please advice.

I don't need that kind of authentication.

In my case if they can look at the page they can use the service. So I rely on the cookies being set.

---

Best wishes,
- Richard
Agile Development Consultant, Practitioner, and Trainer
www.dynamisys.co.uk