AnsweredAssumed Answered

Clarity PPM 13.3 and LDAP (Microsoft AD ) synchronization

Question asked by chrisflynn on Feb 20, 2017
Latest reply on Feb 20, 2017 by chrisflynn

I have a question around Clarity PPM and Microsoft Active Directory synchronization. We had this setup and working perfectly. Our server team reorganized / renamed a couple of the departments in our Active Directory and now Clarity PPM  fails the synchronization anytime a user is placed in our AD group to get synchronized with Clarity PPM if they belong to one of those departments. If I take any of these users, belonging to these departments our of my AD group then the sync job will complete successfully.


My question is, does Clarity PPM (13.3) store the AD structure anywhere within PPM and compares it with the current AD structure and tries to match them? If our organization renames department OU's within Active Directory should the Clarity Administrator have to do anything on the Clarity side as well to incorporate these changes. See the error below from my clarity bg-ca log file.


ERROR 2017-02-20 13:35:14,334 [Dispatch pool-5-thread-8 : bg@STJH1978 (tenant=clarity)] niku.njs (clarity:chrisflynn:10258177__1BF84F1F-04DE-4865-A562-62FE5DEEAA31:LDAP - Synchronize New and Changed Users) Error executing job: 5086284
java.lang.Exception: Synchronize new and changed users job failed: javax.naming.NameNotFoundException: [LDAP: error code 32 - 0000208D: NameErr: DSID-03100238, problem 2001 (NO_OBJECT), data 0, best match of:
 ]; remaining name 'OU=Users,OU=Fisheries and Aquaculture,OU=Fisheries\,Forestry and Agrifoods,OU=Department'
 at com.niku.njs.Dispatcher$
 at java.util.concurrent.ThreadPoolExecutor.runWorker(
 at java.util.concurrent.ThreadPoolExecutor$