Products

Evoq Content Overview Content Creation Workflow Asset Management Mobile Responsive Personalization Content Analytics SEO Integrations Security Website PerformanceEvoq Engage Overview Community Management  Dashboard  Analytics  Member Profile Gamification Advocate Marketing Community Engagement  Ideas  Answers  Discussions  Groups  Wikis  Events Mobile ReadyDNN Support PackagesEvoq: CMS FeaturesEvoq OnDemandCompare DNN's CMS Products

Solutions

Content Management SystemMulti-Channel PublishingDigital MarketingOnline Community ManagementIntranet Software SolutionOur CustomersPrime

Resources

Test DrivesSchedule A DemoDocumentation CenterWebinarsWhite PapersProduct ManualsRequest PricingData SheetsCase StudiesEvoq Preferred Products Content Management Ecommerce Forms Identity Management and Authentication Site Management Social Themes

Partners

DNN Partners Partner Directory Become a DNN Partner Partner Program Overview  Hosting  Implementation  ISV  Training  Competencies

Community

Participate Ask a Question Forums Community Showcase DNN MVP  Program Overview  Lifetime MVPs  Honorary MVPs Subscribe to DNN Digest Advisory Groups  Awareness Advisory Group  Developer Advisory Group  Partner Advisory Group  Technology Advisory GroupLearn Documentation Wiki Community Blog Video Library Project History Development RoadmapDownload DNN Store Language Packs Manuals Nightly BuildsSecurity Policies Security Center

Blog

About

News Press Releases News Coverage Press KitCareersContact DNN

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 ForumsAuthenticationAuthenticationREALLY basic questionREALLY basic question
Previous
 
Next
New Post
4/22/2007 10:34 AM
 
Jeff Hofstetter

Joined: 10/11/2006
Posts: 3

Does the AD module allow a "login" without clicking the login link? What I am looking for is a way that our already-authenticated network users can "login" to our DNN intranet without actually having to click on the login link and enter their network account name and password.

Thanks for reading...jeff
 
New Post
4/22/2007 12:33 PM
 
Shawn Mehaffie

Joined: 1/4/2003
Posts: 2313

I have not used the AD module but if it is the same as the default login module you can do the following.

  1. Add the an AD Login module to the home page (right or left pane).
  2. Set the permissions so that it is visible only to Unauthenticated users.

When the users access the home page they will see the login module, once they login the modue will disappear because they are now authenticated.
 
New Post
4/22/2007 2:56 PM
 
Mike Horton


Joined: 7/16/2003
Posts: 4865

If you follow the steps in this post http://www.dotnetnuke.com/Community/ForumsDotNetNuke/tabid/795/forumid/89/threadid/53005/scope/posts/Default.aspx it'll be setup so that users will be automatically logged in. Please note that this will work only internally on your domain and if the site is also available over the internet users will get a login prompt when they try to connect off site.
 
New Post
4/23/2007 9:38 AM
 
Jeff Hofstetter

Joined: 10/11/2006
Posts: 3

I followed that document quite carefully but I still feel like I am missing some key concept. After making all the changes and restarting IIS, nothing really changed.

When my users access our Intranet, they go to a specific url (intranet.mycompany.com). The home directory for that web site is e:\dotnetnuke. The page that loads is default.aspx which then does all sorts of fun things and finally winds up on the first "tab" of our intranet.

Once they land on the first page, they are NOT logged in. They must click the "login" link and when they do, the login form pops up and asks for username/password.

 Should I be sending the users to a DIFFERENT url that specifically references the WindowsSignin.aspx page instead of sending them to default.aspx? If that is what I am supposed to do, how do I find out the specific url for that page? If I do that, how will they get back to the first "tab"?

mikeh wrote

If you follow the steps in this post http://www.dotnetnuke.com/Community/ForumsDotNetNuke/tabid/795/forumid/89/threadid/53005/scope/posts/Default.aspx it'll be setup so that users will be automatically logged in. Please note that this will work only internally on your domain and if the site is also available over the internet users will get a login prompt when they try to connect off site.
 
New Post
4/24/2007 5:15 PM
 
Oglethorpe

Joined: 3/15/2007
Posts: 7

mikeh wrote

http://www.dotnetnuke.com/Community/ForumsDotNetNuke/tabid/795/forumid/89/threadid/53005/scope/posts/Default.aspx 

Yes, that post has been very helpful to me.  More questions that have cropped up regarding how we have DNN setup and I'm hitting my head to make sure that I have it correct:

  • AD Authentication does work and users are automatically logged in when using the site from the internal network, but users time out and have to re-log back in using the DNN login screen.  When they do so, they do not get authenticated against AD but rather against the DNN user database.  I want to (a) remove the timeout setting so that users will never get logged out; and (b) require the DNN login screen to authenticate against AD.  

    I figure that (a) is handled through one of the many timeout settings -- suggestions as to which one, and what the valid values should be?  I'll assume it's "0" for "no timeout".     Ultimately I want to be able to remove the LOGIN/REGISTER boxes from the DNN screen... although something tells me that I'll end up needing it *somewhere* for admin/host login access.  Also appreciate suggestions on this.

    As for (b), is this really just the difference between Forms and Windows authentication?  If I turn off Forms auth and leave everything else as it is, then I'm assuming that internal users will not be prompted to log in, but external users will be presented with the IIS username/password login box.  This is perfectly acceptable to me, assuming that once a user has logged in that they will not timeout.
  • Still working out how to remove users from DNN once they've been removed from AD.  Suggestions on this also appreciated.
 
 Page 1 of 2
12Next 
Previous
 
Next
HomeHomeDNN Open Source...DNN Open Source...Provider and Extension ForumsProvider and Extension ForumsAuthenticationAuthenticationREALLY basic questionREALLY basic question


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