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 ForumsAuthenticationAuthentication4.5.1 Automatic Windows Login Locks up DNN4.5.1 Automatic Windows Login Locks up DNN
Previous
 
Next
New Post
5/16/2007 11:09 PM
 

My Configuration:

4.5.1 in farming mode on iis 6.0

I am having an issue getting the automatic login to work in the active directory module. My site comes up, but never autologs any users in with their domain credentials.

I am able to successfully see the domain and connect in the authentication window when logged in as host. I get the green ok gif.

In my web.config I have uncommented the Authentication section in http enabler. But any time I change this portion of the webconfig

 <identity impersonate="true" userName="domain\xxxx" password="xxxxx" />
    <authentication mode="Forms">
          <forms name=".DOTNETNUKE" protection="All" timeout="60" cookieless="UseCookies" />
     </authentication>

to

 <identity impersonate="true" userName="domain\xxxx" password="xxxxx" />
    <authentication mode="Windows">
          <forms name=".DOTNETNUKE" protection="All" timeout="60" cookieless="UseCookies" />
     </authentication>

it locks the site up and the webpage will just hang and then time out. Any ideas or anyone have my config in 4.5.1 working, I am getting very frustrated.

Regards,

Mike
  

 

 

 

 
New Post
5/18/2007 4:59 PM
 

Ok got this working. So if anyone is trying to get this going in 4.5.1 Farm mode it does work. Some items to consider if you run into trouble:

1. Changing the authentication mode to Windows will always break, it needs to be in Form authentication always. So

<identity impersonate="true" userName="domain\xxxx" password="xxxxx" />
    <authentication mode="Forms">
          <forms name=".DOTNETNUKE" protection="All" timeout="60" cookieless="UseCookies" />
     </authentication>

People everywhere had been saying this, I just got desperate because I could not get it going in Forms auth mode.

2. If you think you have it configured but the app just wont log you in automatically, it is usually 1 of the following things:

-if you logged into DNN first with your domain credentials, ensure that the user is created properely. In my case, the first time I set up the authentication tab I entered the domain in lowercase. This caused the user to be created and then work when I logged in manually, but then when I updated the domain in capitals like it should be in auth tab, the config was right, but autologin would not work until I deleted the original domain user with the lowercase domain config. So this jacked up all my testing because my test user was the one with lowercase settings. I only figured it out when I had other users log in, and noticed when the account was autocreated, it was in uppercase.

-Ensure that you clear the cache and restart the DNN app in Host settings. Caching seems to play a role in all this if the config was set up improperely at first, like in my situation

Now it works like a champ.

Mike

 
New Post
5/22/2007 7:27 AM
 
 Mike,
I have a few questions on authentication and integration with AD. I have a Intranet 4.5 DNN site running on a 2003 Server in the AD and IIS6. Anonymous access is turned of at the site level and I also have Digest authentication for Windows domain server enabled. I am also running the latest fix for the AD Module. My web.config setting are  <authentication mode="Forms"> ,<identity impersonate="true"/> is commented out. I also have this server-side code from an older post in the signin.ascx page:

 

Sub change(ByVal sender AsObject, ByVal e As EventArgs)

SelectCase txtUsername.Text
Case"admin"
Case"host"
CaseElse
If txtUsername.Text.StartsWith("Domain") Then
'The user added the wrong domain information
If txtUsername.Text.Contains("/") Then
txtUsername.Text = txtUsername.Text.Replace("/", "\")
EndIf
Else
'The user didn't enter the domain so add it for them
txtUsername.Text = String.Format("Domain\{0}", txtUsername.Text)
EndIf
EndSelect
EndSub

Here is the quirk, when I am logged in as host I will get kicked off and then I get automatically logged in as myself. As expected I get an access denied "You do not have access to view this tab within the portal" because I was performing a host function. Also if a user logs off using the logoff what does it take to get them to logged in automatically again? closing the browser, refreshing the page does not work, is it the cookies expiration that does it?

Any help would be greatly appreciated.

Thanks

Dan

 
 
New Post
5/22/2007 11:49 AM
 

Getting kicked off is normal if you have the Authentication line uncommented.

As for what happens when a user logs off..... as far as I can tell it is cookie related.

 
Previous
 
Next
HomeHomeDNN Open Source...DNN Open Source...Provider and Extension ForumsProvider and Extension ForumsAuthenticationAuthentication4.5.1 Automatic Windows Login Locks up DNN4.5.1 Automatic Windows Login Locks up DNN


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