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 ForumsAuthenticationAuthenticationnot automatic login, but okay going to windowssigninnot automatic login, but okay going to windowssignin
Previous
 
Next
New Post
12/7/2008 6:33 PM
 

I forgot to mention in my last post, you need to create a page and name it "Login". Drop the login module on this page. You need this in order for my code sample to work.

 
New Post
3/20/2009 5:28 AM
 

Hy,

I've got the same problem as my previous posters: "Autologon does not work but login works when calling the windowssignin.aspx directly".

I'm really not sure what I'm doing wrong so I'd like to state a list of all settings that i think that need to be set:

  1. IIS: anonymous access to the windowssingin.aspx is turned OFF, Integrated windows-authentication is turned ON
     
  2. The site is running in the local intranet zone. (at least on the clients i try to be logged in automatically)
     
  3. web.config.
    In there i have following configuration:
    3.1;uncommented line: <!-- add name="Authentication" type="DotNetNuke.HttpModules.AuthenticationModule, DotNetNuke.HttpModules.Authentication" / --> the line stated above is NOT showing up in my web.config.
    3.2: provider:
    <providers>
            <clear />
            <add name="ADSIAuthenticationProvider" type="DotNetNuke.Authentication.ActiveDirectory.ADSI.ADSIProvider, DotNetNuke.Authentication.ActiveDirectory" providerPath="~\Providers\AuthenticationProviders\ADSIProvider\" />
    </providers>

    3.3: Authentication
    <authentication mode="forms">
          <forms name=".DOTNETNUKE" protection="All" timeout="60" cookieless="UseCookies" />
        </authentication>
        <identity impersonate="true" userName="XXXX" password="XXXXX" /> // this is needed for security reasons

     
  4. Autologin-Range: I tried multiple variations here. But it does not work for a single ip either:
    4.1; 192.168.1.12 //does noat work
    4.1: The final solution should look like this in my case: 192.168.1.1-192.168.1.254;192.168.3.1-192.168.3.254;192.168.6.1-192.168.6.254;192.168.7.1-192.168.7.254;192.168.9.1-192.168.9.254;192.168.12.1-192.168.12.254
     

Version INFO: DNN: 04.09.01, AD Provider 01.00.04

could anyone please confirm if this is all or if I'm  missing another setting that has to be done to make it work? 
Is there a miss-entry in the settings mentioned above?

Best Regards, Michael

 
New Post
3/20/2009 7:23 AM
 

A couple of comments on this:

- The version of the AD provider that I am running is 1.0.5.1443, so you might want to find the most current version and install that.

- Do you actually need the impersonation line uncommented?  From what I can tell, that is mostly used only if your webserver is in a DMZ.

- For testing purposes, you can leave the autologin-range blank.  This option is mostly for mixed mode, and by entering something in there it provides a login prompt to everyone that it doesn't think is in the authorized range.  By leaving it blank, it will consider everyone to be in the authorized range, which is probably wnat you want for an intranet-only system.

 

 
New Post
3/27/2009 8:51 AM
 

I'm running the same version with the same configuration, of mixed mode windows/dnn authentication.  I have turned on and off the impersonation, and I am using the latested AD provider for DNN 5.0.  I have about 30 users out of 300 (so far) who are having issues with the auto login not working.  I added a link to the windowssignin page as a temporary solution, but for some users, that link doesn't work, and they have to click it several times before it authenticates them at all.  The users are running XP and Win 2000, and IE 6 and IE 7.  It doesn't appear to be a browser issue.  I'm also having issues from different branches from Key West to Naples, so I don't think it's a domain controller issue.  I've tried setting up the AD account in "Authentication Settings" to use even a domain administrator account, but I still have these issues.

I haven't submitted any questions before, so if this should be in a separate thread, please tell me, but this seemed very similar to my issue, and was the most recent thread on this topic. 

 
New Post
3/28/2009 11:35 AM
 

It's relevant to this topic so it's valid to post in this thread. Unfortunately I don't have an answer for you. Because it's working for a large percentage of your users it shows that the problem most likely isn't with the provider or DNN but rather some external factors. Are any of these users that can't get logged in running anything different than those it's working for (i.e. different firewall software, antivirus, etc.)? I don't have easy access to W2K or IE6 anymore but I don't think that should be making a difference. I guess what i'm saying is you need to figure out what makes these ~30 users different from the other ~270.

 
Previous
 
Next
HomeHomeDNN Open Source...DNN Open Source...Provider and Extension ForumsProvider and Extension ForumsAuthenticationAuthenticationnot automatic login, but okay going to windowssigninnot automatic login, but okay going to windowssignin


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