IPC Security

Security methods and authentication

There are a number of authentication methods available. Since an IPC call may initiate a process to which the originator does not have rights, this requires that the authentication method be chosen that suits a successful completion of the process call.

The authentication methods provided:

Integrated Windows
Basic (password sent in clear text)
Impersonate Originator

The method chosen determines what credentials will be passed. 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. The Basic method will pass a connection string containing the username and password from the parent process to the child process for authentication purposes. The Impersonate Originator method will pass the user credentials of the user that started the parent process to the child process for authentication purposes.

Single Sign On

Single sign on requirements may arise if the child process requires a secondary set of credentials to be passed to a LOB system. This would require the originator's, or the form user's credentials to be cached.

If credentials for the backend system have not been cached, this will cause the child and or the parent process to go into error or not complete successfully depending on the call method selected.