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 ForumsAuthenticationAuthenticationActive Directory Provider for DNN 5Active Directory Provider for DNN 5
Previous
 
Next
New Post
1/28/2009 6:14 PM
 

The provider for 4.5.5 (which was built into the DNN core) is from before my time as project lead but I did release some fixes for it as far as synching goes (http://dnn.gmss.org).

With the DNN versions below 4.6.0 synching only occured the very first time a user logged in and their account was created. In the use case you posted that should already work as you're adding them manually to the roles. One of the options when you're doing user managment is to email the user.

 
New Post
2/9/2009 10:50 AM
 

Hello. I get this error in dotnetnuke 5.0 with the 5.0.1 beta of AD.

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

Can't understand AD provider. Running dotnetnuke on 7.0

 
New Post
2/9/2009 11:27 AM
 

It looks like you need to use impersonation in your web.config. If you look at the documenation for the 01.00.04 version of the provider the impersonation setup is the same.

 
New Post
2/9/2009 12:25 PM
 

Thanks. I did just uncomment<identity impersonate=”true”/>, now I dont get error when updating settings.

  • But i get this error on first logon for AD users.

Unknown UserCreateStatus value encountered Parameter name: UserRegistrationStatus

  • Is there anyway sow I dont need to write my domainname/username everytime?
  • I cant logon with AD users when "Hide login controls".
  • The site did not work when disable Anonymous authentication

Christian

 
New Post
2/9/2009 12:56 PM
 

The error on the first logon is a known bug and will be fixed in the next release of the provider.

http://www.dotnetnuke.com/Community/ForumsDotNetNuke/tabid/795/forumid/89/threadid/60815/scope/posts/Default.aspx has a script so that you don't need to put the domain name in front of your username.

What error do you get when you "Hide Login controls"?

I'm not sure what you mean about disabling Anonymous authentication? Can you explain what you attempted?

 
Previous
 
Next
HomeHomeDNN Open Source...DNN Open Source...Provider and Extension ForumsProvider and Extension ForumsAuthenticationAuthenticationActive Directory Provider for DNN 5Active Directory Provider for DNN 5


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