Small width layout Medium width layout Maximum width layout Small text Medium text Large text
     Search
Downloads Downloads Directory Directory Forums Forums Forge Forge Blogs Blogs        Marketplace Marketplace Careers Program Careers
Community › Forums Register  |  

Affordable ASP.NET Hosting Service
  Ads  
 


  Sponsors  

Meet Our Sponsors

DataSprings - Great Ideas. Always Flowing.
R2integrated - formerly bi4ce
Jango Studios - Skins, Modules and Hosting for DotNetNuke
eUKhost.com is commited to offer exceptional UK Windows Web Hosting solutions with quality 24x7 technical support.Our plans support ASP.Net, ASP, ASP.NET Ajax extensions, XML, MSSQL, MySQL, PHP,DNN, multiple domains and Shared SSL as standard.
SmarterTools
The Official Microsoft ASP.NET Website
 


DotNetNuke Forums
 
  Forum  DotNetNuke® Pro...  Authentication ...  Why "DOMAIN\Username" instead of just "Username" in the AD login??
Previous Previous
 
Next Next
New Post 11/19/2007 7:35 AM
User is offline John Hoskins
65 posts
10th Ranked


Re: Why "DOMAIN\Username" instead of just "Username" in the AD login?? 

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 10:16 AM
User is offline Mike Horton
3163 posts
dnn.gmss.org
4th Ranked






Re: Why "DOMAIN\Username" instead of just "Username" in the AD login?? 

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 2:12 PM
User is offline John Hoskins
65 posts
10th Ranked


Re: Why "DOMAIN\Username" instead of just "Username" in the AD login?? 

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 9:28 AM
User is offline Mike Horton
3163 posts
dnn.gmss.org
4th Ranked






Re: Why "DOMAIN\Username" instead of just "Username" in the AD login?? 

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 11:14 AM
User is offline John Hoskins
65 posts
10th Ranked


Re: Why "DOMAIN\Username" instead of just "Username" in the AD login?? 

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.

 
Previous Previous
 
Next Next
  Forum  DotNetNuke® Pro...  Authentication ...  Why "DOMAIN\Username" instead of just "Username" in the AD login??
 


Forum Policy

These Discussion Forums are dedicated to the discussion of the DotNetNuke Web Application Framework.

For the benefit of the community and to protect the integrity of the project, 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 DotNetNuke.
2. Discussion or promotion of DotNetNuke product releases under a different brand name are strictly prohibited.
3. No Flaming or Trolling.
4. No Profanity, Racism, or Prejudice.
5. Site Moderators have the final word on approving/removing a thread or post or comment.
6. English language posting only, please.

 


Customer Connect
Customer Connect provides cutting edge solutions that deliver sales, marketing and customer service results.
www.customer-connect.com
TechNexxus
Business process and technology sourcing solutions delivering superior people, process and value. We have used, and continue to use, DNN successfully in numerous client projects to deliver exceptional value. We are proud to support the DNN team and community.
www.technexxus.com
PartnerPoint | Community of Microsoft Partners
PartnerPoint is one of the largest and most active online communities of Microsoft Partners worlwide with over 8,000 members.
www.PartnerPoint.com

DotNetNuke Corporation   Terms Of Use  Privacy Statement
DotNetNuke®, DNN®, and the DotNetNuke logo are trademarks of DotNetNuke Corporation
Hosted by MaximumASP