IPC Event Wizard - Important Considerations

Processes may surface where the parent process handles one aspect of the process approval and then a child process made available as a default corporate process called when LOB (Line of Business) system processing needs to take place. Not all line of business systems use Windows Authentication and LOB systems external to the company will definitely not use the user's organizational credentials but the external LOB accounts will require the credentials for the respective user account. Fundamentally, the parent process uses one set of credentials to action, and the child process uses a LOB set of credentials and the two credential sets are not the same. If the system is not configured correctly, valid authentication will not take place.

From K2 Workspace, a secondary set of credentials can be cached against a security label using the User Settings page. However, care must be taken when configuring the process call and the Authentication Mode selected as this impacts on whose credentials will be passed.

Managing Authentication Errors

During the life span of the process, there will be authentication errors. This does not always mean a fatal system failure or error but, provided the security is setup correctly the solution to correct the authentication error is simple. The user that started the process may simply need to cache their credentials against the security label for the LOB system.

The authentication errors will surface in the K2 Server error log / error profile.