OIM ldap sync vs ldap connector

OIM LDAP Sync

February 17, 2012 by Ashis
LDAP sync (LDAP Synchronization) is the bidirectional process of exposing the security principals (users, user groups, and roles). This process copies OIM user changes (add, modify, delete) to Oracle Internet Directory (OID) via Oracle Virtual Directory (OVD). LDAP sync runs behind the scene and uses scheduled jobs or reconciliation engine to pull changes from LDAP and event handlers to push data to LDAP.
Is OVD a mandatory element?
It Depends on OIM version.
  • OIM 11.1.1.3.x version requires external OVD server for LDAP Sync.
  • OIM 11.1.1.5 (PS1) versions support both external OVD server as well as inbuilt libOVD (OVD plugin part of OIM ). This means that OVD is an optional component here.
LDAP Sync Vs LDAP connector:
As some of you might be wondering what the difference is, let me make this clear to you that there are some overlap in functionalities between these options and that you have to consciously choose the appropriate one. Here are some of the deciders:
  •  LDAP sync becomes a mandatory element for OIM-OAM integration in the 11g world. In the integrated scenario LDAP sync provides complete password lifecycle management.
  •  LDAP sync is a feature that allows bidirectional synchronization between LDAP and OIM. Don’t expect OIM to manage the LDAP as a resource or target system.
  •  LDAP connector adds the LDAP instance as a resource or target system in OIM. There are a number of actions you can attach around your target systems such as: Workflows, provisioning operations, approvals, requests etc.
  •  LDAP sync does not synchronize Organizations. Users and Roles are the main elements.
  •  Additional features such as Audit, Reporting can only be done with LDAP connector.
  •  Having said all those, I may assert that there can be such requirements that both LDAP sync and LDAP connector might be required for a typical implementation. So brainstorm on your requirement and weigh fine differences of the scenarios before arriving at a decision.
LDAP sync can be setup while installation of Oracle Identity Manager as well as later.
How to Setup LDAP Sync After Install in OIM 11g?

Note on LDAP sync - 
Any changes to users that are made in Ldap directly, these changes will be synched back to OIM.
We know that the changes made to users in OIM are replicated to OID immediately.
This is because the LDAP Sync is bidirectional and it uses scheduled jobs/reconciliation engine to pull changes from LDAP and uses event handlers to push data to LDAP.

Comments

Post a Comment

Popular posts from this blog

VMware fix for Invalid manifest and ova file import failed errors

Image
Recently we got a OVA file for a virtual machine. The vendor instructions were to import the ova file in vmware Workstation, Player for Windows/Linux, Fusion for Mac, and VirtualBox as well.  The instructions were to take the available package and launch the VM with VMware workstation. The package contained  Module.mf, Module.ovf and Module-disk.vmdk and a Module.ova file. The .mf and .ovf file were 2 KB each whereas the vmdk was several gigs. The package also contained a Module.ova file which was several gigs as well. OVF           Open Virtualization Format MF             Manifest file VMDK       Virtual Machine Disk OVA           Open Virtualization Appliance The ovf file is a xml file that contains metadata for the ovf package The mf file contains the SHA1 hash codes of all files in the package The vmdk file is the disk image of the virtual mac...
Read more

Session Timeout in Oracle Access Manager

Image
Session Timeout in Oracle Access Manager (OAM) The session lifetime and Idle timeout entries control how long a user's session is valid. In OAM, a user session is an object which represents an authenticated user. This object is stored in the server memory and if Database session persistence is enabled, this object is stored or available in the database. Each session is unique and is identified by both a userid and Session ID (session identifier), see screenshot below "OAM User Session Management".  A valid session means a user has been authenticated with OAM. A session can have following three states: 1) active 2) inactive 3) expired When a session is created it is in active state and is available as an object in the OAM. After a set time - idle timeout, the session moves or transitions to inactive state. And finally after the Session Lifetime time, the session is marked as expired. Expired sessions are removed from server memory. Read more about Session Lifetime ...
Read more

SOAPUI - import certificate

Image
Note: SoapUI has two versions, one is open source and second Professional version. The open source can be download here . (confirmed link 12/19/2018). SSL Handshake issue:   There is an Issue in SoapUI version 5.3.0 (and 5.2.0 version) with SSL handshake error. It was resolved by updating below in vmoptions file ( refer here ). However, the error that shows up while trying to load wsdl is "Error loading WSDL" as below The fix is to Enable TLS 1.2 protocol for SOAP/REST calls in SoapUI, by ammending the vmoptions file to add the directive for TLS as (-Dsoapui.https.protocols=TLSv1.2). Refer here . Update: Version 5.5.0 does not have this issue. If you are on 5.3.0 better upgrade to 5.5.0 which is available now (Feb 2019). I had above issue as well as another issue reaching to https endpoint. Upgrade to 5.5.0 resolved issue. Select "Check for updates" under the Help menu and you will get option for upgrade. Select upgrade current version and accept all defaul...
Read more