Symptoms
Would like to isolate a new part of the system to operate under a unique service account... Objective is to control all process origination and code execution for the 3 successive async processes using this (limited in scope) account.
Diagnoses
N/A
Resolution
IPC events can have three authentication methods:
1. Integrated Windows: The Integrated Windows method will pass the credentials of the user that the K2 Server is running under to the child process for authentication purposes
2. Basic (password sent in clear text): The Basic method will pass a connection string containing the username and password from the parent process to the child process for authentication purposes.
3. Impersonate Originator: The Impersonate Originator method will pass the user credentials of the user that started the parent process to the child process for authentication purposes.
For IPC processes to be started as this different service account the "Basic" mode can be used to specify this account. Additionally, the Run As option of certain events can be used to run the code as that specified account.
http://help.k2.com/onlinehelp/k2blackpearl/userguide/current/webframe.html_ipc_security_.html
https://www.k2.com/onlinehelp/k2blackpearl/userguide/current/webframe.html_run_as_-_k2_workspace.html
