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.

Objective

We want to force the K2 server to use a specific Domain Controller. How do we do that?

Before You Begin

You will have to modify the LDAP string to use the Domain Controller you want to use, as described in this article:

https://serverfault.com/questions/130543/how-can-i-figure-out-my-ldap-connection-string

We built the string as follows: LDAP://DC1.domain.com/DC=DOMAIN,DC=COM (where DC1.domain.com is the domain controller that needs to be used).

How-to Steps

You can go to K2 Workspace / Management then browse to your User Manager -> K2 security label where you should see all your registered domains with their respective LDAP:// or GC:// strings.

You can edit the LDAP:// or GC:// strings there to only use one Domain Controller as per the above.

If there is only one domain registered then this LDAP string can not be edited, therefore you will have to make changes directly in the K2 database. Please log a support ticket to get help with modifying the XML in the RoleInit column for the "K2" Security Label in the [HostServer].[SecurityLabel] table.