I have DNN 6 installed. So I downloaded the new AD 5.0.0.3 RC. It installed, then I configured, and it found the domain.... So I am not sure what to do after this... how can I add a user fro mthe AD t othe page so they can edit?

when I go into modules, it does not say the AD one is in use... or for tht matther any of the authentication is in use.... can anyone help me out?

ah I just seen this. I was able to login as myself and then I noticed I was a user. I will be using the roles as you described! thanks for explaining all that!

But I do have one issue with this so far.. I want to have a public facing website,  just like dotnetnuke.com , so anyone can go to it. Then I will give my content editors the login page, so that they may edit. So anyone should be able to view without being prompted, and then my content editors open the login page and they enter their username and password and then they do what they need to and logout.

right now for some reason, when someone hits the site it prompts them for a username and password and when they click cancel they can view the site..., or they get the 401, not authorized... it only happens when I install the AD provider... any ideas?

thanks!

A lot depends on how you setup the provider and there are a couple of options you can look at.

If all users (internal/external) are getting the prompt popping up looking for a username/password (I'm making an assumption that this is the IIS popup and not the new JQuery popup generated by DotNetNuke) then the reason is that the site isn't in the trusted or intranet sites list on the internal computers (or you're using Firefox). The solution is to set what IP addresses automatically login in DotNetNuke. In the settings for the provider you'll see Auto-Login IP Address. In this list box you can enter the IPs that you want to automatically login. Depending on how your network is setup you might be able to get away with one IP address if all internal traffic goes through an appliance or you can set it to a range of internal IP addresses. Generally you'll only ever want to use your internal network IPs because external computers aren't on the domain and will always fail trying to authenticate. Also you need to have the site in your trusted or intranet sites list on your network computers and this can be accomplished via group policy.

However, if you don't want anyone to automatically login and have your content editors to login then the easiest solution is to make an edit in your web.config. If you look for the in the and sections of your web.config and comment it out then the AD authentication process will never be fired automatically.