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 Users canAD Users can't login
Previous
 
Next
New Post
4/4/2012 4:39 PM
 

Ditto on Kornelis' post.  My settings for ADAuth (specifically Default Domain) do not stick unless I provide a password as well.  It was driving me nuts until I read this thread.  I have a brand new install of DNN 06.01.04 (127) with DNN_ActiveDirectoryAuthentication 5.0.3 downloaded yesterday.  

 
New Post
3/25/2013 8:09 PM
 
I had this exact situation as well but in my case saving a password did no good. So I entered 127.0.0.1 as an auto-login IP address and now the default domain will stick in the database. (Actually, I saw it in the database but it never hydrated back to the page.)

Cheers.
Weezy
 
New Post
3/26/2013 5:18 PM
 
Mark, this is a known issue (the AD_SUBNET) that I thought was fixed with in the 5.0.5 release and has been fixed in the 5.0.6 RC. I was going to release it this week but another bug has shown up that I haven't fixed yet.
 
New Post
1/10/2017 9:22 AM
 
I know that this is sometime after the original post was created but I have had problems too whereby the 'Default Domain' setting was not working - and the good news is that I've managed to fix it.

Essentially, I had to download the source code and do a bit of debugging. At this time I'm using the latest version (v05.00.06.2) and there appears to be a problem in the solution file:

Components\Config\Configuration.vb

Line 113:

mAutoIP = CType(Null.GetNull(CambrianSettings("AD_SubNet"), mAutoIP), String)

throws an exception and as a result, the code fails to read the mDefaultDomain property (and a couple of other properties too). I've not had a chance to investigate it fully but I fixed it by moving the problem line to the bottom of the function (it could probably be removed as I can't see an AD Subnet option on the configuration screen). It still throws an exception but by then we have read all of the remaining properties.

I know that this fix is not much use if you're not a software developer so hopefully this post might result in a more permanent fix.

Thanks
 
New Post
1/26/2017 10:18 AM
 

Even with a solution provided, the module isn't fixed yet.  Can someone fix this?

or make the solution for a higher version of Visual Studio?

Or isn't there any more support for the AD-plugin?

 
Previous
 
Next
HomeHomeDNN Open Source...DNN Open Source...Provider and Extension ForumsProvider and Extension ForumsAuthenticationAuthenticationAD Users canAD Users can't 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