Products

Solutions

Resources

Partners

Community

Blog

About

QA

Ideas Test

New Community Website

Ordinarily, you'd be at the right spot, but we've recently launched a brand new community website... For the community, by the community.

Yay... Take Me to the Community!

Welcome to the DNN Community Forums, your preferred source of online community support for all things related to DNN.
In order to participate you must be a registered DNNizen

HomeHomeDNN Open Source...DNN Open Source...Provider and Extension ForumsProvider and Extension ForumsAuthenticationAuthenticationPublic IP access and AD authenticationPublic IP access and AD authentication
Previous
 
Next
New Post
9/29/2009 10:13 AM
 

I'm running my site in DNN 5.1. We've configured router to map a public ip to local ip & port. We've an AD with user details. If i enable windows authentication, along with AD, new users from intranet are not able to login(indefinite loop). So i need to enable only AD along with forms, so that any new user from intranet is logged in.  However users from internet are not authenticated it seems. The browser throws dialog box to enter credentials. If they cancel or enter wrong password it does not allow acces. If they enter correct password they are redirected to home page but instead of their name "Register" is displayed. Also in Forums they cannot reply or create new thread. So it seems they are not logged in. I'm stuck here. Please let me know -

1. Whats the best configuration for intranet and public ip access - AD/Windows?Whats the difference in configuration?

2. Why does it display "Register" instead of user name when people access from internet?

 
New Post
9/29/2009 11:15 AM
 

You want to use forms authentication with the AD provider. That's what it's geared for.

If you check the documentation there's an explanation on using the auto-login box in the settings but essentially you want to set it for your internal IP addresses. Once you do this then when external users visit the site it'll be like visiting any website on the internet. See http://www.bus.nait.ca as an example. I've got the AD provider running on there and internal users are automatically logged on. Hit it from outside the domain and you in as a visitor.

As for the other problems....one step at a time as I suspect that there's another configuration problem at play here.

 
New Post
9/29/2009 1:09 PM
 

Thanks Mike. But we need to authenticate external(internet) users based on their AD/Windows credentials, which they enter in the dialog box.

 
New Post
9/30/2009 9:37 AM
 

Right now we've enabled AD along with forms. All internal users (new as well as old) are able to login and browse the site. However when external users hit the public ip, they get a windows creadentials login box. When they enter valid credentials they are allowed to view the site, but they are not logged in tothe application. Their name is not getting displayed. So i think the users are only authenticated against the network and not against the application. Is there any missing configuration. Please help us out.

   <authentication mode="forms">
      <forms name=".DOTNETNUKE" protection="All" timeout="60" cookieless="UseCookies" />
    </authentication>
    <identity impersonate="true" password="****" userName="*****" />

In IIS i've enabled Windows authentication and forms.

 
New Post
9/30/2009 11:51 AM
 

With the setup as I described above external users will still be able to login they'll just have to do it manually. If you go to the site I mentioned above and click on login, if you were a domain user you could enter your username/password and you'd be logged in.

However, if you're set on having your external users have the IIS popup, I'd check your IIS logs for any errors when they attempt to login. What happens if they try to manually login using the DNN process? I had a student all ticked off at me the other day because every time he tried to login it complained about his password. After troubleshooting with him on the phone I found out that he had ZoneAlarm running on his computer and it was blocking his credentials when he entered them. As soon as we disabled it he was able to login just fine so it's possible that something on your external users computers are blocking their credentials.

 
Previous
 
Next
HomeHomeDNN Open Source...DNN Open Source...Provider and Extension ForumsProvider and Extension ForumsAuthenticationAuthenticationPublic IP access and AD authenticationPublic IP access and AD authentication


These Forums are dedicated to discussion of DNN Platform and Evoq Solutions.

For the benefit of the community and to protect the integrity of the ecosystem, please observe the following posting guidelines:

  1. No Advertising. This includes promotion of commercial and non-commercial products or services which are not directly related to DNN.
  2. No vendor trolling / poaching. If someone posts about a vendor issue, allow the vendor or other customers to respond. Any post that looks like trolling / poaching will be removed.
  3. Discussion or promotion of DNN Platform product releases under a different brand name are strictly prohibited.
  4. No Flaming or Trolling.
  5. No Profanity, Racism, or Prejudice.
  6. Site Moderators have the final word on approving / removing a thread or post or comment.
  7. English language posting only, please.
What is Liquid Content?
Find Out
What is Liquid Content?
Find Out
What is Liquid Content?
Find Out