How to provision users in bulk to Active Directory Group with OIM

How to provision users in bulk into Active Directory Group with Oracle Identity Manager OIM.

Oracle Identity Manager (OIM) can integrate with Active Directory as a target system for provisioning users in Active Directory. With Oracle Identity Manager as the central Identity Management system one can manage, provision, deprovision or terminate user accounts as per the policy defined in OIM. The OIM connector for Microsoft Active Directory User Management is required for this integration. With this connector in place OIM can manage the lifecyle of user accounts in Active Directory.

 There are situations where there is a need to provision hundreds of users. This is a typical scenario where one needs to bulk provision users into a Active Directory Group via OIM. (instead of provisioning users one by one manually which can be tedious and time consuming). This post deals with provisioning users to a Group in Active Directory (provisioning users to AD is a related but different use case).

 Here lets assume the scenario is that AD users are managed by OIM, in other words OIM does all the provisioning operations into AD.

If OIM (Oracle Identity Manager) is provisioning users to AD then, it is assumed the (1) you have OIM connector for AD User Management already installed [refer OIM Connector Guide for Active Directory User Management] and AD exists as a Resource Object in OIM and (2) the user already exists in OIM and AD. Now you have to provision the user into the AD group - so you need to create an access policy in OIM which will have a rule to assign the AD group as provisioning operation/task. Of course this is assuming that you done the number (1) pre-requisite of having a OIM connector for AD User Management and AD exists as a Resource Object in OIM. The AD group will be assigned to the users as an entitlement. Here is good blog which provides all the steps of creating a creating such an Access Policy (the blog is for OIM 11gR PS3 11.1.2.3). The only difference between this blog and your requirement is that this blog gives an example of LDAP group in OUD, whereas your requirement is that of a Group in AD.


Make sure you have the two pre-requisites (1), (2), already in place as given above. The Access Policy will be applied to users as defined above (so it could be thousands of users that can be provisioned into an AD Group). Same steps would apply for any other target Directory, such as OID or OUD.

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