There is no need to try to rebuild the DNN project to run it locally. Just use the Install package to get DNN running.

If you feel that you must rebuild the solution, there are some instructions available, including a video on YouTube from Peter Donker, I think.

But ... why do you want to rebuild?

Hello Joe,

I want to rebuild because I integrated the dotnetcasclient in my website based on dnn, and i have some problems with administrator rights (unable to edit the page and add extensions), I want to debug this issue.

Philippe

I assume that you want to do this for authentication. If that's the case, it might make more sense to create an authentication provider that can be installed into DNN the way that other authentication providers are installed. It would seem to me that using the framework of DNN and the extension points that it provides is the natural way to go.

Yes, it is for the autentication.

I found the auth provider facebook, etc, but I don't understand how to implement these extensions points. the dotnetcasclient is based on httphandlers. beginwebrequest, etc..

 

 

Well, we are on even footing here. Until a few minutes ago, I had never heard of CAS!

You might want to take a look at the Active Directory authentication provider: https://github.com/DNNCom...DNN.ActiveDirectory.

I believe that there are also some oauth providers floating around.

You'll probably also find some old blog posts, mostly from Joe Brinkman I think, that discusses authentication providers. I have a dim memory of a discussion of oauth.

I actually created a custom authentication provider. It was a simple modification the standard DNN provider, so there wasn't a lot of customization and no attempt to talk to an external system. But ... you can start there and replace the guts of the authentication part with a "DoMyStuff" call that would handle all of that.

 

My key point is ... don't mess with the internals of DNN but use the extension points provided.  You'll save yourself a lot of grief that way.

Thank you for your reply and your advises.

I will give a look to the standard DNN provider and try to find more information about auth provider.

 

Found this: https://github.com/intelequia/dnn.casprovider

Thank you, I did search for months and I didn't find it ....

Unfortunately this solution is not compatible with our CAS server, our server is providing login page and all password and login confirmation logic.

My implementation with the dotnetcasclient (based on forms authentication) is working well with users and users roles to access pages, modules, etc..

I have problems to access the /API/personaBar (Micro Services ???) .

The debugging message in the explorer is 401 : “Authorization has been denied for this request.”

May be I have to call some extra functions to allow the current user logged to use the personaBar ?