Michael, thanks for the post. You'll get no argument from me that the code needs to be cleaned up. The provider was originally written as an add-on by another user for DNN 1 maybe but definitely for DNN 2 using the .NET 1 framework. I inherited it when I took over the project a little over a year ago and it's always been my plan to do a complete re-write of the code to get it up to (at minimum) .NET 2 standards. The problem has been time. Between the 9 to 5 (I have to laugh as I write that), bug fixes for the current code, and life in general I haven't gotten to it. After every release I say to myself, "Ok, that's it, it's stable. I'm starting from fresh code for the next release." only to hear about some bug or another that needs fixed right away.

I do have plans for the next release and the major one will be that it runs under Intergrated pipeline so that we can get rid of those calls. That alone is going to be a major code change and another reason to just start from scratch.

hi mike....

I was using DotNetNuke version 4.09.00 and i needed ADSIAutheticaion provider  available on DotNetNuke.com

At the time of installion it was giving somekind of javascript error..so i couldnt proceed with the installation ahead after license varification...

after that i went to the install zip...extracted it..in one of the text file they asked to update the some code for fckeditor in web.config for my website.....rest i followed the steps in documentation and it worked fine...

please convey this little step to other users on forum

Thanks for your infomative and intime responses.....they are really informative

I am not a programer, so I don't understood in which direction sync ocures in web-inisde solution? AD -> DNN or DNN -> AD?

I have similar needs as seen in thread http://www.dotnetnuke.com/Community/Forums/tabid/795/forumid/89/scope/posts/threadid/290261/Default.aspx

As I see AD provider is best when you have an intranet environment (LAN or VPN). When you have a lot of external/internet users, which logs in from
different IP adresses AD provider it is almost useless in my point of view (if someone feels otherwise feel free to correct me ). Lets consider my case. We are non profit organization. From sponsors we get server Win2003 on which I installed DNN, i.e. AD, IIS, SQL and DNN on the same server, which is not very clever nor secure, but we don't have resources nor needs for enterprise security. Although AD is a good way of storing user information. In the future we may deploy other solutions such as mail, which requires authentication too, and we may use AD. Thats why I planned on using AD authentication for DNN website. But only recently Mike clarified that AD provider is one way (see forum link above), i.e. reading form AD and writing to DNN SQL database, no storing in AD (no two way sync). I am not sure what is the reasoning to copy initial AD account info to DNN and then using it locally... It seams DNN is replicating AD funtion, but not fully, only for the current website/portal. In my case I would like users to access the website with AD account, to be able to change password and other info for AD account, because users don't have dirrect access to the server with AD by any other means (at least yet )...

Sumarizing i would offer to make AD provider in the following way:

1. If AD provider is used, AD account should not be recreated/copied in DNN SQL database. It just adds additional security/sync difficulties.
2. All queries/writes/updates are performed directly to AD

These are just my thoughts comming from my experience and my needs, developers decides, what is really needed.

Thanks

Benediktas