Hi,

I've a couple of issues/questions:

1. I've upgraded DNN from 4.8.2 to 5.6.1 (following the upgrade path 4.9.5->5.4.5->5.5.1->5.6.1) and installed AD extension 5.0.2. I've setup the configuration for local intranet as documented, including impersonate. We have existing users in the system and I added domain name in front of their user name in both Users and ASPNET users tables. Users can login successfully the first time. But, after they click on the logout button, they are no longer able to login automatically unless they clear the cookies. They have to use Windows Login on the web site and enter their domain id and password. Most of our users are using IE 8. However, when they enter the windowssignin.aspx path in the url, they can login automatically. Is there something wrong with the setup? I've followed the documentation and am using Delegation, setup Auto-login IP addresses (to see if that made a difference). Hide Login Controls is not checked. IIS is configured for Integrated Windows Authentication for WindowsSignin.aspx.

2. We've a SaaS solution hosting a lot of DNN sites. Some folks wanted their site to be integrated with their AD infrastructure. If we setup a VPN IPSec tunnel, we should be able to connect to their AD with the Active Directory provider, right? Are there any particular ports that need to be allowed to make this happen?

Thanks for your help!
Prakash

Thanks for the reply. We usually expire the cookie as soon as the user logs in for some of our apps to overcome certain issues like this. Guess that doesn't apply here.

On the second one, typically with SaaS becoming more and more the standard for application hosting, it is not uncommon for users asking for AD integration and not having to remember passwords for applications they use every day. Having said that, yes, there's always that fear of some one trying to login to the domain. What would they do? How can they get in? I know we want to be safe than sorry but, it usually is the customer's call. If they want us to allow querying their AD to authenticate users, perhaps they're not as concerned.

Thanks for clarifying!

You could modify the code so that it's reset immediately but then nobody would ever be able to logout period. That would mean that if there's ever a time when you needed to login as someone else (say the DNN Admin or Host account) you wouldn't be able to.