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 ForumsAuthenticationAuthenticationWhy "DOMAIN\Username" instead of just "Username" in the AD login??Why "DOMAIN\Username" instead of just "Username" in the AD login??
Previous
 
Next
New Post
11/19/2007 10:35 AM
 
John Hoskins

Joined: 8/11/2003
Posts: 67

Thanks.  I don't use manual login.  I'm not even sure manual login would work in my environment since the password isn't stored in AD.  I would have assumed that any manual login would check against the DNN user table which would only contain the username (minus the domain) before going out to AD like the automatic AD authentication does.  Does it go the other way when you manually login and verify the user against AD before pulling up their DNN account? 
 
New Post
11/19/2007 1:16 PM
 
Mike Horton


Joined: 7/16/2003
Posts: 4865

Prior to DNN 4.6 when it was a single signin module it did check the DNN database first but when the code was separated I changed it so that it would always authenticate against the AD. I did so for a couple of reasons. First to catch any password changes and, two, to force synchronization if it was selected.
 
New Post
11/19/2007 5:12 PM
 
John Hoskins

Joined: 8/11/2003
Posts: 67

Hmmm.  Good points.  Would it be possible to check against DNN first to see if the UserName is there, then query AD based on the GUID to do the password check and sync?  This would eliminate the need for the domain name.
 
New Post
11/20/2007 12:28 PM
 
Mike Horton


Joined: 7/16/2003
Posts: 4865

You mean the GUID from DNN? I don't know if that'll work. The way it works now DNN is checked to see if the user does exist so that it knows whether to it needs to add a new user or just authenticate the current user. Then there's a section that authenticates a user against the domain (IsAuthenticated(Entry as directoryEntry, LoggedOnUserName, Password)) and this is where it fails if the username isn't in the Domain\Username format. I was looking at it last night and put together a fix that gets the Domain name but that'll only really work in a single domain installation. I have to work around for situations where there's multiple domains which is difficult to code for when I don't have multiple domains to test for.

 
 
New Post
11/20/2007 2:14 PM
 
John Hoskins

Joined: 8/11/2003
Posts: 67

The UserInfo GUID gets set with the Directory Entry's NativeGuid (.GUID = entry.NativeGuid).  You should then be able to add another Function which uses the NativeGuid as the filter.  I've done this for a couple of other field values which I need to use to search for AD accounts.  This should be a unique value across multiple domains.

If you need help testing in multiple domains, let me know - you should have my email address at work from the code I sent you.
 
 Page 3 of 3
Previous123 
Previous
 
Next
HomeHomeDNN Open Source...DNN Open Source...Provider and Extension ForumsProvider and Extension ForumsAuthenticationAuthenticationWhy "DOMAIN\Username" instead of just "Username" in the AD login??Why "DOMAIN\Username" instead of just "Username" in the AD login??


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