Setting the Security Mode
Setting the Security Mode
This content is no longer actively maintained. It is provided as is, for anyone who may still be using these technologies, with no warranties or claims of accuracy with regard to the most recent product version or service release.
The security mode for workflow is set on the ProcessDefinition object. The Mode Property of the IProcessDefinition Interface tells the workflow engine the mode in which you want the workflow to execute. In Restricted Mode, you are not able to use Component Object Model (COM) objects in the ActionTable, or to create objects in memory from script. In Privileged Mode, you can use COM objects in the ActionTable and coCreate almost any object in script. If you do not set the Mode Property, it defaults to zero (0), which is neither restricted nor privileged. Your application will not run with a zero value for the mode property. You must set the security mode explicitly.
The Workflow System Account needs to have sufficient privileges in the workflow folder. If you register events for the workflow folder, provide at least read privileges. If the workflow event sink will make changes to the folder contents, the Workflow System Account requires read and write privileges in the folder.
The topics in this section discuss the security modes and how the workflow event sink enforces security.
Send us your feedback about the Microsoft Exchange Server 2003 SDK.
Build: June 2007 (2007.618.1)
© 2003-2006 Microsoft Corporation. All rights reserved. Terms of use.