E1: LDAP: Frequently Asked Questions on LDAP Batch Synchronization (R9200040)
(Doc ID 2004942.1)
Last updated on APRIL 01, 2019
Applies to:JD Edwards EnterpriseOne Tools - Version SP23 and Prior and later
Information in this document applies to any platform.
To track bugs mentioned in this document use:
This document provides some questions and answers in reference to LDAP Batch Synchronization (R9200040)
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!
In this Document
|Questions and Answers|
|Question 1: How is data synchronized between LDAP and EnterpriseOne?|
|Question 2: Does the R9200040 synchronize only new users?|
|Question 3: How to delete the users from EnterpriseOne when LDAP is enabled?|
|Question 4: Is there a way to run R9200040 to select and delete only certain users?|
|Question 5: If LDAP is turned off/disabled, can using R9200040 keep F98OWSEC passwords synchronized with LDAP?|
|Question 6: If there are existing P0092 records, what happens to these records when running R9200040?|
|Question 7: LDAP UBE R9200040 Produces Blank Reports|
|Question 8: When running the R9200040 for LDAP Synchronization, why is the report coming out blank and not updating any users?|
|Question 9: Does LDAP Bulk Synchronization report (R9200040) use the "User Search Base" and "User Search Filter" parameters from P95928 when synchronizing the users?|
|Question 10: Does R9200040 require that LDAP is enabled in the jde.ini and that there is an active LDAP configuration in P95928?|
|Question 11: If a record for an LDAP user already exists in the various E1 tables, does R9200040 skip that user in the synchronization of any table for which the user already exists or does it delete and re-add the user to the various E1 tables?|
|Question 12: If the LDAP configuration specifies that roles are managed in E1 not LDAP, does the R9200040 bypass the synchronization of any role updates, e.g. F95921 table?|