Configuring the Nodinite LDAP Adapter for Microsoft BizTalk Server
Unlock the full potential of your Nodinite LDAP Adapter for Microsoft BizTalk Server with proper configuration. This guide covers essential post-installation steps, including license management, SSO setup, and send handler configuration, ensuring a secure and seamless integration experience.
✅ Centralized license management for compliance and control
✅ Flexible SSO support for secure authentication
✅ Easy configuration of send handlers for robust operations
License
You must provide a valid license key to activate the product. Licenses are available as either full or trial versions.
Each license includes two key properties:
- Customer Name: The licensee's name, which appears in the XML response message summary within the
<LicenseInformation>element. Enter this value exactly as provided by Integration Software (case sensitive). - License key: The unique, encrypted license key for your organization.
Add this information to the config file (IS.BizTalk.Adapters.LDAP.Windows.ClientTestUtility_v1_0.exe) for the Test Client and to each send handler associated with the Nodinite LDAP Adapter for Microsoft BizTalk Server in the BizTalk administration console.
Repeat the process for each send handler by selecting the handler and clicking 'Properties'.
Associate the appropriate Host Instance(s) as Send Handler.
Enter the License information for each handler.
Click Apply/Ok when you are done editing.
If the license information is invalid, you will see the following error dialog:
Example of invalid license information error.
Contact support@nodinite.com to obtain a valid license or resolve any issues with this mandatory step.
Image example from the BizTalk Server administration console.
Important
You must apply the license key for each new and/or changed BizTalk host instance associated with the adapter.
For example: If you have 2 send handlers associated with the adapter, you must enter the license key information twice—once for each send handler.
SSO
This step is only required if you intend to use the SSO feature.
The LDAP Adapter 1.0 targets BizTalk Server 2013 R2, but supports all BizTalk Server versions from 2010 onward. The SSO assembly loaded at runtime may differ by environment. The .NET framework version is 4.0.
To determine your SSO version, check the Server and Administration values at:
HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\ENTSSO
The assembly Microsoft.BizTalk.Interop.SSOClient.dll can also be used to verify the SSO version. The default location is C:\Program Files\Common Files\Enterprise Single Sign-On. For BizTalk 2013 R2, the file version is 9.0.2096.0 and the .NET version is 9.0.1000.0.
Manual changes:
If your BizTalk version is not 2013 R2, you must edit your BizTalk configuration file with an assembly redirect as shown below.
Important
Always back up your configuration files before making changes. Invalid files may prevent BizTalk from starting. See How to Back Up The BizTalk Server Configuration for guidance.
Files to edit (usually in C:\Program Files (x86)\Microsoft BizTalk Server 201x):
- BTSNTSvc.exe.config – for 32-bit enabled host instances
- BTSNTSvc64.exe.config – for 64-bit enabled host instances
Change the version number according to your installed SSO Assembly version. See the table below for details.
BizTalk 2013 R2 example:
<configuration>
…
<runtime>
<assemblyBinding xmlns='urn:schemas-microsoft-com:asm.v1' appliesTo='v4.0.30319'>
<dependentAssembly>
<assemblyIdentity name='Microsoft.BizTalk.Interop.SSOClient' publicKeyToken='31bf3856ad364e35' culture='neutral' />
<bindingRedirect oldVersion='0.0.0.0-1000.0.0.0' newVersion='7.0.2300.0'/>
</dependentAssembly>
</assemblyBinding>
…
Important
Change both 32 and 64 bit versions on all nodes.
Target environment:
| BizTalk Version | Change required | SSO Assembly Version | SSO Product Version |
|---|---|---|---|
| BizTalk 2020 | No | ||
| BizTalk 2016 | No | ||
| BizTalk 2013 R2 | Yes | 9.0.1000.0 | 9.0.2096.0 |
| BizTalk 2013 | Yes | 7.0.2300.0 | 9.0.1865.0 |
| BizTalk 2010 | Yes | 5.0.1.0 | 6.0.4219.0 |
If you changed the configuration files, restart the host instances to apply changes.