You would probably have to create a custom WorkflowSchedulerService so that you can create threads in which you impersonate the appropriate identity before executing the WaitCallback delegate as part of the Schedule call.
Thanks for the response. But here I have to define a different permission set not impersonate another identity.
I tryied creating another AppDomain and executing the workflow into the new AppDomain but it seems not to work properly. The Workflow live always in the same AppDomain.
Pierre
Executing the workflow under a custom permission set
Executing the workflow under a custom permission set
Kim Carlsen
I found the solution: no solution. The workflow can run only on a FullTrust enviroment (http://windowssdk.msdn.microsoft.com/en-us/library/ms734559.aspx).
Thanks,
Pierre
mikey905
Jonas1980
Thanks for the response. But here I have to define a different permission set not impersonate another identity.
I tryied creating another AppDomain and executing the workflow into the new AppDomain but it seems not to work properly. The Workflow live always in the same AppDomain.
Pierre