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
See the instructions documentation (attached PDF) and https://community.appian.com/w/the-appian-playbook/520/ldap-synchronization for more information.
Hello everyone,
I’m working with a customer who recently migrated from an on-premises setup to a cloud environment. Since the move, they’ve been experiencing significant slowness during LDAP synchronization. Specifically, the LDAP User Sync with Usernames plugin smart service is taking approximately 8 minutes to process just 7 usernames.
Has anyone encountered similar performance issues post-migration? Are there any recommended alternatives to this plugin or best practices to improve sync efficiency in a cloud environment
How do we configure exception for some users in this plugin?
Hi,I am also interested in madhavia0002's question : is there an update planned to resolve these risks ?Best regards,
Jean-Jacques
We see LDAP tools reported in the health check report , any remediation for this?
adusersynchronizationwithusernamesMediumLDAP Tools (adusersynchronizationwithusernames) references deprecated Appian APIs [deprecated] com.appiancorp.suiteapi.common.ServiceLocator.getContentService(com.appiancorp.services.ServiceContext) [deprecated] com.appiancorp.suiteapi.common.ServiceLocator.getDiscussionMetadataCoreService(com.appiancorp.services.ServiceContext) [deprecated] com.appiancorp.suiteapi.common.ServiceLocator.getPortalAdministrationService(com.appiancorp.services.ServiceContext) [deprecated] com.appiancorp.suiteapi.common.ServiceLocator.getProcessAnalyticsService2(com.appiancorp.services.ServiceContext) [deprecated] com.appiancorp.suiteapi.common.ServiceLocator.getProcessDesignService(com.appiancorp.services.ServiceContext) [deprecated] com.appiancorp.suiteapi.content.ContentOutputStream.close() [deprecated] com.appiancorp.suiteapi.content.ContentService.getInternalFilename(java.lang.Long) [deprecated] com.appiancorp.suiteapi.content.ContentService.notifyUsersCreation(java.lang.String[]) [deprecated] com.appiancorp.suiteapi.content.ContentService.upload(com.appiancorp.suiteapi.knowledge.Document, java.lang.Integer) [deprecated] com.appiancorp.suiteapi.forums.DiscussionMetadataCoreService.notifyUsersCreation(java.lang.String[]) [deprecated] com.appiancorp.suiteapi.personalization.UserRank.getId() [deprecated] com.appiancorp.suiteapi.personalization.UserRank.setId(java.lang.Long) [deprecated] com.appiancorp.suiteapi.portal.AdministrationService.notifyUsersCreation(java.lang.String[])
Is any limitation with LDAP Sync Application (How many roles we can configure for sync?)
What are the possible reasons behind users getting failed sync. Getting one bot user in usersFailed output
having the same error did you reach any solution
Has anyone encountered discrepancies in how ldapSearch() functions vs LDAP Profile Synch? We are seeing cases where a specific filter returns certain results in ldapSearch() but different results in LDAP Profile Synch.
Specifically, doing a filter for "not a group member" ((!(isMemberOf=X)) is not being respected in the Synch but is in the search.
Anyone has any idea?