We are implementing a WebAPI using DNN (not sure if it's still called Service Framework or if that was the old MVC version). We are having some problems with authentication though.

Something like this seem to work with the current user having correct permissions (being a member of the group):

[DnnAuthorize(StaticRoles = "TheRole")]
[HttpGet()]
public HttpResponseMessage Test()


So authentication and WebAPI in general should be working.

However, this does not work:

[DnnModuleAuthorize(AccessLevel = DotNetNuke.Security.SecurityAccessLevel.Host)]
[HttpGet()]
public HttpResponseMessage Test()

[DnnModuleAuthorize(AccessLevel = DotNetNuke.Security.SecurityAccessLevel.Admin)]
[HttpGet()]
public HttpResponseMessage Test()


Even when logged in as Superuser you get permission denied.

Is this a bug or is the SecurityAccessLevel no longer supported?

BTW; is there anyone but us using the WebAPI in DNN?

I guess that the lack of responses here probably answers the question "BTW; is there anyone but us using the WebAPI in DNN?"

Glad to hear that. May I ask how your route mappings are set ut to handle WebAPI in DNN allowing usage of WebAPI according to best practice using simple and complex parameters?

I've found that something like this works best:


mapRouteManager.MapHttpRoute(
moduleFolderName: "MyWebAPI",
routeName: "default",
url: "{controller}/{action}/{id}",
defaults: new { id = RouteParameter.Optional },
namespaces: new string[] { "MyWebAPIControllers" }
);