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 ForumsAuthenticationAuthenticationLogin is a bit strange...Login is a bit strange...
Previous
 
Next
New Post
10/29/2008 12:23 PM
 

I now have the new AD authentication module up and running on a bunch of different portals, and in use by hundreds of people...  It works great!

There are a few quirks though that I have yet to be able to resolve...

I have most of the people logging in using a button I put on the page that redirects them to the WindowsSignIn.aspx file.  That works great from inside of the district, and from outside of the district they now get a login box where they can type in their name using two different formats (DOMAIN\Username or Username@DOMAIN.COM).

The issues I'm running into right now:

1.  No matter what I enter into the "Auto-login IP Address" field, I cannot get users "automatically" authenticated simply by visiting the website from the local Intranet.

2. When I click the link to log into the website using the WindowsSignIn.aspx file, all works well, I'm logged in with Admin privileges.  When I log in, using the same account, using the standard login box, I'm authenticated but I'm not part of the admin group anymore.

 

 
New Post
10/29/2008 11:06 PM
 

Hey Dan.... Long time no see.

1. Take a look at the site log and see what IP addresses are coming into the site. At work all web requests are passed through an appliance so that internal wired clients all appear to come from one IP while wireless come through another and external users come from whatever IP they've got. So in my case I just had to set the one IP and it worked fine. Perhaps this is the same in your situation.

2. This is odd and I'll have to try to duplicate it as both methods eventually uses the same code for synchronization and the admin role is skipped.

 
New Post
10/30/2008 8:57 AM
 

Yeah, we had some serious staffing reductions over the last year, and I've had tons and tons more work piled upon me.  Haven't had much time at all to play around with DNN like I wanted to. *sigh*  Anyways...

1.  Here is an example of a recent log entry: 2008-10-30 12:46:19 10.20.1.4 GET /DesktopModules/AuthenticationServices/ActiveDirectory/WindowsSignin.aspx - 80 - 10.20.5.187 Mozilla/4.0+(compatible;+MSIE+7.0;+Windows+NT+5.1;+Q312461;+.NET+CLR+1.0.3705;+.NET+CLR+1.1.4322;+.NET+CLR+2.0.50727;+InfoPath.2) 401 2 2148074254
The webserver is at 10.20.1.4, and this particular workstation is at 10.2.5.187, so it looks like it is resolving the address correctly.  This is one of 6 "local" subnets, we are running a class addressing scheme on our internal network with a class B subnet mask.

2. Yeah, that one struck me as pretty strange also.  I was playing around with the menus, trying to figure out a way to disable "standard" login, or at least get it to work properly so I don't have to keep telling everyone NOT to click on the login link, but to click on the button instead (that gets old pretty fast).  So, standard login is for now disabled, Windows login is the only login available with the account login module.

 

 

 
Previous
 
Next
HomeHomeDNN Open Source...DNN Open Source...Provider and Extension ForumsProvider and Extension ForumsAuthenticationAuthenticationLogin is a bit strange...Login is a bit strange...


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