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 ForumsAuthenticationAuthenticationProblem with windows authenication to ADProblem with windows authenication to AD
Previous
 
Next
New Post
10/25/2006 1:34 PM
 

When I go into the Authenication selection under admin and attempt to start the windows authenication installation here is the trouble i am having:

 

Windows Authenication: checked

Syncronize Role: Unchecked

Provider: ADSIAuthenicationProvider

Authentication Type: Delegation

Root Domain: dc=this,dc=that,dc=com

And a username and password that have access to the AD on the network.

 

Here is the error I get back:

Error: Windows Authentication is currently unavailable.
DotNetNuke.Services.Exceptions.ModuleLoadException: Object reference not set to an instance of an object. ---> System.NullReferenceException: Object reference not set to an instance of an object. at DotNetNuke.Security.Authentication.ADSI.Utilities.AddADSIPath(String Path, Path ADSIPath) at DotNetNuke.Security.Authentication.ADSI.Utilities.GetRootEntry(Path ADSIPath) at DotNetNuke.Security.Authentication.ADSI.Utilities.GetRootEntry() at DotNetNuke.Security.Authentication.ADSIProvider.GetNetworkStatus() at DotNetNuke.Security.Authentication.AuthenticationController.NetworkStatus() at DotNetNuke.Modules.Authentication.AuthenticationSettings.cmdAuthenticationUpdate_Click(Object sender, EventArgs e) --- End of inner exception stack trace ---

 

Does anyone have any ideas on why i would be getting this error?  Thank you for any help!

 
New Post
10/26/2006 11:41 AM
 
Have you edited web.config yet?
 
New Post
10/27/2006 4:53 PM
 
Well i found the issue Actually what I had to do was use

Root Domain: this.that.com

instead of

Root Domain: dc=this,dc=that,dc=com

For some reason the DC format was giving an error.
 
New Post
11/2/2006 2:50 PM
 

I had similar issues. I'm no VB wizard (give me C# any day), but the case sensitive code in the constructor for DotNetNuke.Security.Authentication.ADSI.Configuration looks fishy to me. Try using capital "DC=" to see if that fixes it too.

Try

'Temporary fix this setting as TRUE for design, to be removed when release

mConfigDomainPath = authConfig.RootDomain

mDefaultEmailDomain = authConfig.EmailDomain

mUserName = authConfig.UserName

mPassword = authConfig.Password

mAuthenticationType = CType([Enum].Parse(GetType(AuthenticationTypes), authConfig.AuthenticationType), AuthenticationTypes)

' IMPORTANT: Remove ADSIPath, to be added later depends on accessing method

mRootDomainPath = ADSI.Utilities.ValidateDomainPath(mConfigDomainPath)

mRootDomainPath = Right(mRootDomainPath, mRootDomainPath.Length - mRootDomainPath.IndexOf("DC="))

Catch exc As Exception

mProcessLog += exc.Message & "<br>"

End Try

 
Previous
 
Next
HomeHomeDNN Open Source...DNN Open Source...Provider and Extension ForumsProvider and Extension ForumsAuthenticationAuthenticationProblem with windows authenication to ADProblem with windows authenication to AD


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