- 3 minutes to read

Nodinite BizTalk LDAP Adapter Release Notes

Stay informed about the latest enhancements, compatibility updates, and bug fixes for the Nodinite BizTalk LDAP Adapter. This page provides a transparent history of improvements, new features, and important upgrade guidance for your integration projects.

✅ Continuous updates for new platforms and directory services
✅ Compatibility with the latest Windows Server and Active Directory versions
✅ Clear upgrade instructions and breaking change alerts
✅ Enhanced API, XSLT, and debug support for developers

Make sure to revisit this page as we continuously develop new versions

1.0.0.62

  • (new) Support for eDirectory
  • Verified support for Windows Server 2022
    If your DC is W2k19 or W2k22, you must update to this version.

1.0.0.60

  • (bug) GetDomainControllers method has been corrected
  • (bug) Enable method for users did not enable the users
  • (change) Support for Windows Server 2019.
    If your DC is W2k19, you must update to this version or later.
  • (change) Additional trace code
  • (change) Documentation was moved from Word/PDF -> Online

We always strive to preserve compatibility. If you are running 1.0.0.35 or later, you can safely update using these instructions. If you are still running a version <=34, you may need to update your solutions since returned content is now always in lower case. See the breaking change note below.

Older versions

= .44

  • (new) REST API built on ASP.NET Core 2.0.6. Review discussion for details.
    Call from Azure Logic Apps using the on-premise data gateway, Mule, or any custom solution. Use the same XML requests and code. We recommend using custom XSLT mappings (not BizTalk mapper) to future-proof your integrations.
  • (new) Add support for values with non-valid XML characters. A property encoded="true" is set for properties with encoded values. The response XSD is also updated.
  • (bug) If the number of properties was zero for a returned Record, the adapter failed.

= .45

  • (bug) Changed the internal order of operations by changing values for some core properties (some values must be set before others)
  • (change) If no flags (add/remove) are provided as part of the Request, the internal method to change flags is not executed at all (no need)

= .46

  • (bug) Passwords are now always masked in the debug output

= .47

  • (bug) If the AD Domain did not have proper replication configured, the adapter crashed with a null reference exception for some AD-related queries. Added code to provide helpful information and avoid exceptions.

= .48

  • Added more internal exception handling and debug output for invalid/incomplete requests to facilitate resolving reported problems (which now usually only happen due to incomplete/invalid requests)

= .49

  • (bug) Adding or removing flags always enabled a user account. This behavior now honors the disable flag if you add it.

At the time of this release note, there are no longer any reported unresolved bugs with our LDAP Adapter.

Breaking changes

If you are running on versions pre .34, there is a breaking change regarding the response. Previous responses were camel-cased. Post .34 versions return lower case names for the properties returned.

.34
Example response pre 1.0.0.34 version

.35
Example response post 1.0.0.34 version