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 ForumsAuthenticationAuthenticationAdditional AD Login considerationsAdditional AD Login considerations
Previous
 
Next
New Post
3/10/2008 8:31 PM
 

I have a few minor questions all along the same thread...

1. Is there a way to login  using the ad user account without using the syntax 'domain\user'... in other words can we store the 'domain\' somewhere and have the username appended on 'Login'

2. A user can login as 'domain\user' and also as user@domain.com --- same user however two separate accounts are created in the DNN user database. Is there a way to control this or prevent one method over another?

3. Perhaps I don't understand this field... Auto-login IP Address (Optional):  I placed the subnet of the network I reside into this field and was under the impression that my AD user crednetials of the computer I am logged into would pass to the DNN portal and auto log me on. Am I understanding this correctly? if yes why does this not work... if no what function does this field provide?

 

 
New Post
3/11/2008 12:53 AM
 

1. There is a post here that contains a script that you can add to the Login.ascx that will do what you're looking for. I've got it bookmarked at work so I'll post it tomorrow. If I don't just remind me.

2. Ummmmm, I thought I'd taken care of that. Is it doing so in the 01.00.03 version as well? I'll have to check the code when I get to work

3. When you say subnet do you mean subnet mask (just checking to make sure we're on the same page)? It was a toss up between having subnet the subnet mask vs. the actual IP addresses and I went with the IP addresses themselves as for a couple of reason. One was that I thought it would be easier for the "everyman" to figure out and two, it was easier to code for . I can pull the IP address out of the information passed to the server but would have to use code to figure out the mask. So what you should be able to do is something like the following: On my home network all my DHCP server hands out addresses between 192.168.0.1 to 192.168.0.50 so in that box I put 192.168.0.1-192.168.0.50. Any system connecting to the DNN install that pass that IP address to the install will automatically log in but any system not in that range (which would be all external as there aren't any valid internet addresses in that range) would bypass the redirect to WindowsSignin.aspx. So yes you understand it correctly but you may not have entered the correct information.

 
New Post
3/15/2008 3:01 PM
 

Mike thanks for your help thus far.

Still looking for the code to update the Login.ascx  file so our users do not have to put the domain name in the login field.

Thanks.

 

 
New Post
3/15/2008 9:31 PM
 

Doh!!! http://www.dotnetnuke.com/Community/ForumsDotNetNuke/tabid/795/forumid/89/threadid/60815/scope/posts/Default.aspx has the script except now it goes into DesktopModules/Authentication/ActiveDirectory/Login.ascx.

 

 
Previous
 
Next
HomeHomeDNN Open Source...DNN Open Source...Provider and Extension ForumsProvider and Extension ForumsAuthenticationAuthenticationAdditional AD Login considerationsAdditional AD Login considerations


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