Skip to main content
Hi,

Provided that all your trusts are functioning and set up correctly it should not be a problem.
To allow authentication to a different domain you will need to add an extra Active Directory connection string to your K2Server.config file and your K2Studio.config file.

K2Server.config

<K2Server>
  <DataSources>
    <DataSource Path="LDAP://DC=geo,DC=corp,DC=int" NetBiosName="GEO" Type="ActiveDirectory" />
    <DataSource Path="LDAP://DC=aag,DC=corp,DC=int" NetBiosName="AAG" Type="ActiveDirectory" />
  </DataSources>


K2Studio.config

<K2Studio>
  <DestinationRule>
    <DataSources>
      <DataSource Path="LDAP://DC=geo,DC=corp,DC=int" NetBiosName="GEO" Type="ActiveDirectory" />
      <DataSource Path="LDAP://DC=aag,DC=corp,DC=int" NetBiosName="AAG" Type="ActiveDirectory" />
    </DataSources>


Hope this helps!

JohanL
Pl guide, how we will be installing our k2.net if our requirement is as
follows:

We have an empty root domain corp.int, this is the root domain and
have no user accounts in side,

And then we have two child domains under this root domain, one is
geo.corp.int and other is aag.corp.int ; and we want users of
both the domains to use the k2.net features or in other words k2 can see all users in both the domains; so if we will be installating k2.net in root domain corp.int then it can see all users accounts in all child domains under empty root domain

Please help us

Reply


View our Community Site Map

Nintex Community Sitemap
Terms & ConditionsCookie settings