Host account can login to a portal and access other portals without the need to re-login.  For example, a host account logins the parent portal “acme.com”.  The host account then visits the child portal “acme.com/child”.  DNN does not prompt host account to login to see the Host menu.

If a regular user login the parent portal “acme.com” and then try to access the child portal “acme.com/child”, DNN will require user to login the child portal.

Could someone please point out where in the source code DNN magically allows host to bypass login to the child portal but requires regular user to login (even if the regular user already login the parent portal)?

Thanks in advance

Also, if what you're after is some sort of "single sign-on" then there are at least a couple of addon modules that will open up cross-portal logins without altering the core.

ah, ok i see what you mean. In that case I suggest that the correct place to look is Library\HttpModules\Membership\MembershipModule.vb . This is a httphandler that checks each web request to see if the user is logged in, what rights they have and whether or not they've changed portals. If you look at the OnAuthenticateRequest method, we try to detect when a user moves between portals and expire their cookie (this is how dotnetnuke allows portal aliasing for multple seperate portals). I believe your problem is that your module is using an aspx page to update it's visitor counter. As that file is an aspx file it passes through this authentication check, and as it's seen as a portal change (as the aspx page existing in a folder outside "portals"). I would suggest that you change your aspx page to be a handler i.e. an ashx.

Cathal