This article was created in response to a support issue logged with K2. The content may include typographical errors and may be revised at any time without notice This article is not considered official documentation for K2 software and is provided “as is” with no warranties.
The problem occurs in the deployment step - it is picking up the account on my local machine and not the account details I have entered.
The process should be using the admin account on the clients domain.
You are unable to deploy K2 for Visual Studio / K2 Studio due to an incorrect permission level, but the permissions are fully set in K2 Workspace for the user.
On K2 Studio you have the connection settings as below:
K2 Studio/VS Studio uses a number of connection strings to connect to K2 (i.e. for environment libraries).
Change these connection strings to not use Integrated Authentication:
A number of categories on K2 Object Browser use connections strings that are set to use integrated authentication, for example: