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 ForumsAuthenticationAuthenticationWhat are your settings for impersonation?What are your settings for impersonation?
Previous
 
Next
New Post
8/10/2010 8:43 AM
 
I just finished reading a dozen or so posts about impersonation, and I am still unclear how to get it to work.
DNN 5.4.4 w/ AD provider version 5.0.2
IIS 6 on Windows 2k3 standard server.
.NET 3.5


I am using a service account specifically for impersonation. The AD account has change access to all the required directories on the web and system folders.
I had originally setup DNN with AD authentication and used the service account to setup the the AD extension in DNN. Worked great, service account sees the DC and authenticates, Green check marks, etc.. users all authenticate and all is peachy.

I then make the required changes for impersonation.
1) I changed the web.config file adding impersonation with the service account credentials.

<!-- Forms or Windows authentication -->
<identity impersonate="true" userName="DOMAIN\UserID" password="pa$$word"/>
<authentication mode="Forms">
<forms name=".DOTNETNUKE" protection="All" timeout="60" cookieless="UseCookies" />
</authentication>

2) I changed the Identity in the ASP.NET App Pool to the service account credentials.
3) I refreshed the App Pool and restarted my web service.
4) Open my browser and added the http:// address to my trusted sites list.
5) Browse to my intranet site and immediately get prompted with a Windows logon box for my windows credentials.
6) I enter my credentials multiple times and it fails with "Error: Access is Denied."
7) Just for giggles I tried multiple user ID's and multiple URL addresses including the WindowsSignin.aspx.

Do I need to change my App Pool identity? And shouldn't it work with any domain ID in my App Pool as long as they have the correct permissions?
Thanks...
 
New Post
8/10/2010 9:30 AM
 
You shouldn't need to set the App Pool identity. Other than that you've got it setup the exact same as I do.
 
New Post
8/10/2010 10:05 AM
 
Thanks for your reply Mike!  I am glad I had it right, except for the App Pool identity.
Unfortunately, I am pretty sure I need to use a domain ID for the App Pool identity so that I can access some UNC paths for network resources.  (example: DMX document management)
Do you know of a configuration that will work with a domain ID in the App Pool?
Thanks..
 
New Post
8/10/2010 11:43 AM
 
Is it the same user account per chance? When you use impersonation in the web.config it should still be able to connect to UNC paths as long as the user has permissions to it. When a site in the default configuration (take DNN out of the equation and just think of any old .NET website) it usually runs under NETWORK SERVICE and if it tried to connect to a network resource it would do so as NETWORK SERVICE. If you used impersonation in the web.config it then sends all traffic as the user you used for the impersonation. So, I think setting the App Pool identity and using impersonation accomplishes the same thing but I could be wrong.
 
Previous
 
Next
HomeHomeDNN Open Source...DNN Open Source...Provider and Extension ForumsProvider and Extension ForumsAuthenticationAuthenticationWhat are your settings for impersonation?What are your settings for impersonation?


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