LDAP Tools

Overview

This Plug-in provides the ability to update Appian user profiles from data retrieved from an LDAP server. The data that can be synchronized include all the default user profile fields except the username (e.g. first name, last name, address, phone, supervisor, title, etc…) as well as the custom fields.

Key Features & Functionality

  • LDAP User Profile Synchronization (Smart Service) - available in the Process Modeler under Integration Services > Connectivity Services
  • LDAP Sync Process Model (Sample Process Model) - will need to be tailored and tested based on identity management requirements
  • ldapSearch() Function - returns an array of LDAP attributes for a specific search query

See the instructions documentation (attached PDF) and https://community.appian.com/w/the-appian-playbook/520/ldap-synchronization for more information.

Anonymous
  • I am trying to use ldapSearch() function from a expression editor and trying to pass the paraments the function needs. I am getting below error. Any Idea what might be the issue? 

    ERROR com.atlassian.plugins.rest.common.error.jersey.ThrowableExceptionMapper - Uncaught exception thrown by REST service: loader constraint violation: when resolving method "org.slf4j.impl.StaticLoggerBinder.getLoggerFactory()Lorg/slf4j/ILoggerFactory;" the class loader (instance of org/apache/felix/framework/BundleWiringImpl$BundleClassLoader) of the current class, org/slf4j/LoggerFactory, and the class loader (instance of org/apache/felix/framework/BundleWiringImpl$BundleClassLoader) for the method's defining class, org/slf4j/impl/StaticLoggerBinder, have different Class objects for the type org/slf4j/ILoggerFactory used in the signature
    java.lang.LinkageError: loader constraint violation: when resolving method "org.slf4j.impl.StaticLoggerBinder.getLoggerFactory()Lorg/slf4j/ILoggerFactory;" the class loader (instance of org/apache/felix/framework/BundleWiringImpl$BundleClassLoader) of the current class, org/slf4j/LoggerFactory, and the class loader (instance of org/apache/felix/framework/BundleWiringImpl$BundleClassLoader) for the method's defining class, org/slf4j/impl/StaticLoggerBinder, have different Class objects for the type org/slf4j/ILoggerFactory used in the signature

    Thanks

  • I am currently looking at the User record upgrade documentation and I noticed that in the record sync notes, the user record sync cannot be triggered except from specified OTB user smart services or where the userService public Java API has been used in the related plugin.
    I cannot find any reference to the userService public Java API inside the source for this plugin and so I would conclude that this plugin will not trigger the record synchronization.
    Am I correct in my findings above?
    Does anyone have any experience they would like to share or recommend a course of action that would result in the triggering of a User record sync when utilising this smart service?
    Thanks in advance.

  • Had similar issues, but after updating the plugin from 1.2 to LDAP-tools-1.5.1; the issue was resolved.

  • We found that the Users Deactivated output from the LDAP User Profile Synchronization With Usernames smart service is always returning 0, even when the Usernames Deactivated returns data for our current implementation. Is this intended or is there some issue there? We are currently on 1.5.1 in 22.2 Appian.

  • Our LDAP configuration is working from admin portal for authorization. however, we are facing connectivity issue (SSL handshake exception) while using LDAP tool this plugin-in. Would like to know location of the certificate this plugin is using it, and any associated configuration required.

  • Did the error appear in an older version of the plug-in and v1.5.1 fix it?

  • The latest plugin version v1.5.1 works fine with Appian version 22.4.

  • After we switched from Appian 21.4 to Appian 22.4 on Dev Environment - There is an error in LDAP Process - There is a problem with task "LDAP User Profile Synchronization" in the process "LDAP Group Synch - LDAP Users" . Should we use updated LDAP app/or/and plug-in LDAP jar file?

  • This version fixed the issue. Confirmed. Thanks!

  • v1.5.1 Release Notes
    • Fixes issue with Application package format