Topic
Errors start appearing on forms, Workspace, Management and Designer if K2 site's .NET Trust Level is changed from Full to Medium.
Instructions
K2 requires Full trust because of the following:
- Services (e.g., Identity/Sts/Windows), SmartObjects, SmartForms, and workflows, require Full Trust to operate correctly due to the following: Dynamic Assemblies and Reflection:
- K2 dynamically loads and executes assemblies for workflows, SmartObjects, and integrations, which requires unrestricted permissions available only under Full Trust.
- Custom Code Execution: K2’s extensibility features, such as custom service brokers, custom workflows, and rules engine execution, depend on permissions unavailable in Medium Trust.
- Third-party Integrations: K2 integrates with platforms like SharePoint, Microsoft SQL Server, and CRM, which require Full Trust for seamless communication and access.
- Configuration File Access: K2 applications often access and modify configuration files at runtime, which is restricted under Medium Trust.
- IIS-Level Handlers: Certain features, such as WCF services (e.g., .svc files) and other IIS-managed components, require Full Trust to function.
When Medium Trust is applied, K2 components may fail to operate. Examples include:
- Identity/Sts/Windows: Unable to process authentication requests.
- Autodiscover Service: Fails to locate or configure necessary components.
- SmartObjects and Workflows: Errors or failure to execute key functionality due to insufficient permissions.
Therefore making it not possible to configure Medium trust.