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

HomeHomeGetting StartedGetting StartedInstalling DNN ...Installing DNN ...First Run Problems - EventQueue Issue ?First Run Problems - EventQueue Issue ?
Previous
 
Next
New Post
11/7/2006 12:38 PM
 

Hi all, reading this thread makes my head turn round, but maybe this article helps: it implements a solution to the problem:

http://aspalliance.com/650_CodeSnip_Impersonation_in_ThreadPool_Worker_Threads

HTH, Pieter

PD: Personally, I have had many problems when installing fresh DNN 4.3.x instances on both XP sp2 and Win2003 Server. I have an older DNN 3.x instance running on my host and it never fails (it uses .NET 1.1). I think that lately the issues with security and different types of accounts is really getting too complicated, above all for non-security experts. What one actually does in their desperation is open the doors completely first to make it work and then one should close it bit by bit but mainly that will not happen; so goodbye security measurements!

 
New Post
11/9/2006 6:57 PM
 

Please delete this if it ends up being a double post. Not sure if the first attempt worked.

I think that I may have found a solution for the schedule part of the problem. Below are the steps that I have carried out

Add a new property to the Common.Globals (Global.vb)

Private _ApplicationIdentity As System.Security.Principal.WindowsIdentity

Public Property ApplicationIdentity() As System.Security.Principal.WindowsIdentity

Get

Return _ApplicationIdentity

End Get

Set(ByVal value As System.Security.Principal.WindowsIdentity)

_ApplicationIdentity = value

End Set

End Property

Then in the UrlRewriteModule.vb within the OnBeginRequest add the following code

' Check that the services are running under the current user

If DotNetNuke.Common.ApplicationIdentity.Name <> System.Security.Principal.WindowsIdentity.GetCurrent().Name Then

DotNetNuke.Common.ApplicationIdentity = System.Security.Principal.WindowsIdentity.GetCurrent()

End If

Note that I could not use the Init because at this point it was still processing under the Network Service account.

Then in the Schedule Provider within the ProcessGroup.vb within the Start method introduce the following code (the code that I have added is in italics

Try

Process.ScheduleHistoryItem.Succeeded = False

Dim changedIdentity As Boolean = False

Dim wi As System.Security.Principal.WindowsImpersonationContext

If System.Security.Principal.WindowsIdentity.GetCurrent.Name <> Common.ApplicationIdentity.Name Then

wi = Common.ApplicationIdentity.Impersonate()

changedIdentity = True

End If

Process.DoWork()

If changedIdentity Then

wi.Undo()

End If

This changes the identity that the schedule code (DoWork) is done under. Since most of the time the website is running under the correct account the setting the new property should only happen once in the Begin event mentioned. This can then be used as the main account to run the scheduled services under.

Not sure if it is the best solution however, it does work.

 
New Post
11/10/2006 2:42 AM
 
Thought that I would dd a bit more info. First I have not had a chance to test this on my hosting provider site. It has just been tested locally. Also below is kind of what happens

App Starts
Any Schedule Service that runs when the App Starts runs under the original account, so in this setup it runs under Network Service
Any future Scheduled Services run under the account that the website runs under.

I will try to look at this some more over the weekend.
 
New Post
11/24/2006 6:24 AM
 

Hi,

I have little knowledge of the IIS/SQL requirements needed to avoid getting a windows login prompt when visiting DotNetNuke sites (higher that DNN 322 - as 322 seem to work fine), but this could perhaps be part of the problem.

I would be more or less impossible to explain and convince my hosting provide to change anything related to their IIS or MS SQL configurations, so I home very much this will be "fixed" in DNN - or even better a workaround provided that I can implement myselft in the DNN file system.

Will keep my eye on this thread for a solution..

Thanks for pointing me to this thread (from: http://www.dotnetnuke.com/Community/ForumsDotNetNuke/tabid/795/forumid/118/threadid/85104/scope/posts/Default.aspx)

/Leon

 

 
New Post
11/25/2006 12:19 PM
 

Tanzy,

Have you had a chance to test this on a host yet?  I am eagerly awaiting the results.

 
Previous
 
Next
HomeHomeGetting StartedGetting StartedInstalling DNN ...Installing DNN ...First Run Problems - EventQueue Issue ?First Run Problems - EventQueue Issue ?


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