Skip to main content


 

Symptoms


Cross domain authentication
 

Diagnoses


When using the following documentation to configure cross domains:

http://help.k2.com/onlinehelp/k2blackpearl/userguide/4.6.5/webframe.html_k2_domains.html

When using multiple domains it is also important to modify the Workspace Web site to authenticate for each domain. To do this, follow these steps:

Open web.config file corresponding to the Workspace Web site, typically located at C:Program FilesK2 blackpearlWorkspaceSite
Add a new AD Connection String in the connectionString section. For example:



In the membership section add a new provider pointing to the newly added connection string. The name of the string needs to be unique and match the other example in Step 2. For example:


enablePasswordReset="false" enableSearchMethods="true" requiresQuestionAndAnswer="false"
applicationName="/" description="Default AD connection" requiresUniqueEmail="false"
clientSearchTimeout="30" serverSearchTimeout="30" attributeMapUsername="sAMAccountName"
name="AspNetActiveDirectoryMembershipProvider_Domain2" type="System.Web.Security.ActiveDirectoryMembershipProvider,System.Web,
Version=2.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a" />


So when you have configured this you get the following error below:

Error:

Initialization failed before PreInit: The entry 'AspNetActiveDirectoryMembershipProvider' has already been added.


 

Resolution

The AspNetActiveDirectoryMembershipProvider name needs to be a completely name to the first one that was entered. After this you shouldn't face any more issues.




 
Be the first to reply!

Reply