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 ForumsAuthenticationAuthenticationHow may I activate Windows + Local authentication on DNN 4.5.1How may I activate Windows + Local authentication on DNN 4.5.1
Previous
 
Next
New Post
5/14/2007 12:00 PM
 

Hi everybody.

In advance sorry if my questions are "stupid" but I'm beginner in the DNN World and, after some researchs, I need help for the following subject.

I have installed DNN 4.5.1 and the portal is up. Now I would like to enable windows authentication AND local authentication.

mixed mode = The possibility to allow authentication from LDAP server AND from local database user. Correct ?

If yes,I would like activate "mixed mode" authentication on my portal.Then, my first question is : what's the correct and comlete definition in the web.config file for activate "Mixed mode" ?

The server where the DNN portal is installed isn't member of the domain (because the server is in DMZ).

Then my second question is : may do that ?

Thank you in advance for your responses

Etienne

 
New Post
5/15/2007 12:46 AM
 

First Etienne, the only "stupid" question is the question that isn't asked.

You're right on the money on what mixed-mode means. How to activate it? Basically if you followed the instructions in this post (http://www.dotnetnuke.com/Community/ForumsDotNetNuke/tabid/795/forumid/89/threadid/53005/scope/posts/Default.aspx) except don't uncomment the <authentication.... /> line in your web.config would put you in mixed-mode.

I've seen a lot of posts where people have run into problems getting authentication to work because the server wasn't a member of the domain but I haven't had a chance to setup an enviroment similar to that since I took on the project lead role. All I can suggest is that you give it a shot and see what happens. Right now my focus is getting the AD provider "separated" from the DNN Core and once that's done I'll hopefully be able to work on setting up as many different testing environments as I can.

 
New Post
5/15/2007 5:29 AM
 

I'm trying to follow the instructions in the suggested post, but I'm turning around.

In the post suggested above, the first step is "Admin settings" (the DNN configuration for windows authentication).

Then I apply (I hope) all the suggested settings ad I receive the following response :

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 ---

Then I understand that I need to active "mixed mode" in the web.config file as following :

Before change :
<!-- Forms or Windows authentication -->
       <authentication mode="Forms">
       <forms name=".DOTNETNUKE" protection="All" timeout="60" cookieless="UseCookies" />
       </authentication>
<!--     
       <identity impersonate="true"/> 
      <authentication mode="Windows">
      </authentication>
-->

After change (if my understanding of the configuration for mixed mode is correct)
<!-- Forms or Windows authentication -->
       <authentication mode="Forms">
       <forms name=".DOTNETNUKE" protection="All" timeout="60" cookieless="UseCookies" />
       </authentication>
       <identity impersonate="true"/> 
<!--     
      <authentication mode="Windows">
      </authentication>
-->

In this case, I'm note able to acces the portal :

 

 

DotNetNuke Error: - Version 04.05.01


User does not have permission to perform this action.

FYI, My server is actually in the domain, for an easyer environment.

Have you any suggestion for me ?

Thank you  in advance

 
New Post
5/15/2007 11:01 AM
 

You may not have to uncomment the <identity impersonate="true" /> but if you do you'll probably have to add a userName="domain\username" password="password" to it (<identity impersonate="true" userName="somedomain\mikeh" password="password" />. There are some other changes that need to be done but first see if the connection works.

 
New Post
5/15/2007 11:02 AM
 

You may not have to uncomment the <identity impersonate="true" /> but if you do you'll probably have to add a userName="domain\username" password="password" to it (<identity impersonate="true" userName="somedomain\mikeh" password="password" />. There are some other changes that need to be done but first see if the connection works.

 
Previous
 
Next
HomeHomeDNN Open Source...DNN Open Source...Provider and Extension ForumsProvider and Extension ForumsAuthenticationAuthenticationHow may I activate Windows + Local authentication on DNN 4.5.1How may I activate Windows + Local authentication on DNN 4.5.1


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