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 ForumsAuthenticationAuthenticationAD auth multiple accounts created from browser promptAD auth multiple accounts created from browser prompt
Previous
 
Next
New Post
7/13/2011 11:49 PM
 
I'm using DNN5 for a customer's website and I've got AD authentication working to create accounts.  But I just noticed that when they get a browser prompt for the username and password, if they enter their username in as <domain>\<username> their DNN username gets created as <domain>\<username>,  but if they enter it in without the domain part, i.e <username> their ad account gets created with just their usersname and no domain prefit

This is ok (I guess), but what I've found is that when you enter the username once with the domain and once without via the browser prompt it creates two accounts.

Both seperate accounts.  In the AD authentication config, I've tried it both with the default domain filled in and without but it works the same.
Is there a way to stop this, i.e recognise the same account regardless of whether the domain is entered or not?

Or at least force the creation of accounts with one standar or the other?
 
New Post
7/14/2011 11:31 AM
 
Check this thread.  It's kinda old but still relevant.
http://www.dotnetnuke.com/Resources/Forums/forumid/89/threadid/60815/scope/posts.aspx
 
New Post
7/14/2011 5:25 PM
 
Thanks Mark,  I had a read through it an it could possibly be a solution.  I did some testing yesterday and another issue we're having is the error below on the AD extension page.  Has anyone experiences this?

This error only seems to occur on servers, i.e my local development version doesn't get it and the problem with the AD accounts doesn't happen on my local machine.   Users can log on with and without their domain in the browser prompt and it still creates their username in DNN with the domain prefix.  The difference with the server instances is most likely permissions.

ModuleId: -1
ModuleDefId: -1
FriendlyName:
ModuleControlSource:
AssemblyVersion: 5.4.1
PortalID: 0
PortalName: PCMS Web Portal
UserID: 5
UserName: uninet\karagit
ActiveTabID: 46
ActiveTabName: Extensions
RawURL: /public/pcms/Admin/Extensions/tabid/46/ctl/Edit/mid/364/PackageID/102/Default.aspx
AbsoluteURL: /Public/PCMS/Default.aspx
AbsoluteURLReferrer:
UserAgent: Mozilla/5.0 (Windows; U; Windows NT 6.0; en-US; rv:1.9.2.18) Gecko/20110614 Firefox/3.6.18 ( .NET CLR 3.5.30729; .NET4.0E)
DefaultDataProvider: DotNetNuke.Data.SqlDataProvider, DotNetNuke.SqlDataProvider
ExceptionGUID: 70589982-ccd4-4f9a-9491-ec5cfac3b079
InnerException: Access is denied.
FileName:
FileLineNumber: 0
FileColumnNumber: 0
Method: System.DirectoryServices.DirectoryEntry.Bind
StackTrace:
Message: DotNetNuke.Services.Exceptions.ModuleLoadException: Access is denied.---> System.Runtime.InteropServices.COMException (0x80070005): Access is denied.at System.DirectoryServices.DirectoryEntry.Bind(Boolean throwIfFail)at System.DirectoryServices.DirectoryEntry.Bind()at System.DirectoryServices.DirectoryEntry.get_IsContainer()at System.DirectoryServices.DirectoryEntries.ChildEnumerator..ctor(DirectoryEntry container)at System.DirectoryServices.DirectoryEntries.GetEnumerator()at DotNetNuke.Authentication.ActiveDirectory.Settings.CheckPipelineMode()at DotNetNuke.Authentication.ActiveDirectory.Settings.Page_Load(Object sender, EventArgs e)--- End of inner exception stack trace ---
 
New Post
7/15/2011 12:22 AM
 
Theo, the user name should be created with the Domain name proceeding it. That's how the provider creates accounts (to prevent username collisions in situations where the site is both internal (AD users) and external (Internet users).

Did you install the AD provider for your customer or did they already have it installed? If they installed it is there a chance that they had someone modify it? There is code in the provider to strip the domain name out but I never implemented it because I couldn't find a nice way to strip the domain name from current accounts (so running into the exact same problem you're seeing), handle username collisions (as mentioned in my first paragraph), or to put the domain name back in the case that an administrator decided to revert back to having the domain name in front).

As for Mark's post.... that code is all part of the code behind in the provider now. That's why there's the option to set the default domain name. If it's set and the user logs in without the domain name it injects it.
 
New Post
7/15/2011 1:35 AM
 
Mike,

Thanks for your response.  I installed the provider so there's no chance that anyone has modified it.   There have been no core changes made to the DNN that we are using (5.4.1).

It's very odd because user accounts are being created and user details are coming across from AD but in many cases the username doesn't have the domain pefix.  I've done several other AD site for other customers and I've never seen it create users without the domain prefix.

Any ideas as to the error on the AD extension page?

Thanks,
Theo
 
Previous
 
Next
HomeHomeDNN Open Source...DNN Open Source...Provider and Extension ForumsProvider and Extension ForumsAuthenticationAuthenticationAD auth multiple accounts created from browser promptAD auth multiple accounts created from browser prompt


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