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 ForumsAuthenticationAuthenticationQuestionQuestion
Previous
 
Next
New Post
11/8/2006 8:20 AM
 
dstruve wrote

How do I deal with people who go to the sites and have no need to log on, are they going to be prompted automatically?

You are referring to a "mixed-mode" scenario, which has proven to be a royal pain for me.  I've been running it here in that mode for almost a year and a half, and it isn't pretty.

Like Mike was saying, you need to leave that one line in the web.config commented out, otherwise EVERYONE will be prompted to login, even the general public.  I found that if a non-domain user visits your website from the Internet, they will get a domain login prompt.  If they click on cancel, it puts a cookie on their computer and doesn't prompt them again until that cookie gets erased.  But, after a short discussion on this with co-workers, it was quite quickly decided that that is simply not acceptable for a semi-public website.

So, if you leave the DotNetNuke.HttpModules.AuthenticationModule line commented out in the web.config (and leave it set for forms-based authentication, you can have a mixed-mode scenario.  However, you will NOT be automatically logged into the website simply by visiting.  You will either have to log in as DOMAIN\Username or visit the WindowsSignIn.aspx URL.   (By the way, I believe that this is the reason why I cannot get portals to work with AD authentication.)

I got around this by forcing student accounts to log in via the WindowsSignIn.aspx file as their start page in IE, and push that URL out as a favorite for everyone else.  I also created a custom login page that allows for both (http://www.mapsnet.org/Home/Login/tabid/52/Default.aspx) to make it a bit simpler.  So far, this is working, but I'd like to get the AD module updated someday to allow for these things without the work-arounds.  (I guess I'll have to learn how to code in .Net.)

There was a post about a year ago or so, back in the ASP.Net forums, about how someone was able to modify IIS to redirect someone to different URLs based off of their IP address, but I lost the printed copy, and haven't gone back to try and find it again online.  That was another approach I was going to try and take.

 

 
New Post
11/8/2006 8:21 AM
 
dstruve wrote

How do I deal with people who go to the sites and have no need to log on, are they going to be prompted automatically?

You are referring to a "mixed-mode" scenario, which has proven to be a royal pain for me.  I've been running it here in that mode for almost a year and a half, and it isn't pretty.

Like Mike was saying, you need to leave that one line in the web.config commented out, otherwise EVERYONE will be prompted to login, even the general public.  I found that if a non-domain user visits your website from the Internet, they will get a domain login prompt.  If they click on cancel, it puts a cookie on their computer and doesn't prompt them again until that cookie gets erased.  But, after a short discussion on this with co-workers, it was quite quickly decided that that is simply not acceptable for a semi-public website.

So, if you leave the DotNetNuke.HttpModules.AuthenticationModule line commented out in the web.config (and leave it set for forms-based authentication, you can have a mixed-mode scenario.  However, you will NOT be automatically logged into the website simply by visiting.  You will either have to log in as DOMAIN\Username or visit the WindowsSignIn.aspx URL.   (By the way, I believe that this is the reason why I cannot get portals to work with AD authentication.)

I got around this by forcing student accounts to log in via the WindowsSignIn.aspx file as their start page in IE, and push that URL out as a favorite for everyone else.  I also created a custom login page that allows for both (http://www.mapsnet.org/Home/Login/tabid/52/Default.aspx) to make it a bit simpler.  So far, this is working, but I'd like to get the AD module updated someday to allow for these things without the work-arounds.  (I guess I'll have to learn how to code in .Net.)

There was a post about a year ago or so, back in the ASP.Net forums, about how someone was able to modify IIS to redirect someone to different URLs based off of their IP address, but I lost the printed copy, and haven't gone back to try and find it again online.  That was another approach I was going to try and take.

 

 
New Post
11/8/2006 10:23 AM
 

Thanks everyone for teh feedback!!!

Dan,  perhaps we can work together on this solution since I am a programmer and our needs are closely tied.


DotNetNuke Search Engine
ASP.Net Search Engine
Email me to add your favorite sites to the search List.
 
New Post
11/8/2006 10:53 AM
 
dstruve wrote

Dan,  perhaps we can work together on this solution since I am a programmer and our needs are closely tied.

Sounds good to me!  Where do we start?

 
New Post
11/8/2006 11:56 AM
 
I'd be interested in your results as well as I'm in the same boat.
 
Previous
 
Next
HomeHomeDNN Open Source...DNN Open Source...Provider and Extension ForumsProvider and Extension ForumsAuthenticationAuthenticationQuestionQuestion


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