How to create a user for a future Start Date in OIM

How to create a user in Oracle Identity Manager (OIM)/Oracle Identity Governance (OIG) with a future "Start Date" and ensure user account is only enabled on the "Start Date"

User accounts are created in Oracle Identity Manager (OIM) as users are on-boarded or join the organization. There are typical use cases when users are given a joining date or the day when a user reports to duty. The user should be able to login to the systems when he starts his duties. Hence, the user account and login should be enabled for the user so that they can successfully login to the systems.

The user account should only be in the enabled or in Active state on the day user is officially supposed to start. In other words the account which has been created for the user should be in a Disabled state until the day of start. The security rule is never to have an active account or Entitlements for Users who are not active in the system. The user account is Active on the day user joins the organization or office. Same rule for users who leave the organization or have been off-boarded - to disable the user account and his Entitlements.

In Oracle Identity Manager for future start date, see this OIM lifecycle reference where this is documented as follows - If the Start Date of a user is in future, then the create process creates the user in a disabled state. And when the User's start date is in effect, then the user is marked enabled in the system and user is now able to login and use the system.

 
                                       Figure: User Lifecycle
 

When creating a user who has a start date set in the future, OIM will create the user in a “Disabled State" until the Start Date and provision target accounts as determined by the access policy and set them to Disable State. Note here, OIM creates the user but sets it to a Disabled State. (An account in disabled state cannot be used for login). Now when the day of the "Start Date" is reached, meaning on the day of "Start Date", the “Enable User After Start Date” scheduled job, evaluates the Start Date attribute, and enables all users whose start date has passed and at the time the job is run.

Here is the scheduled task which ensures user account is Active so user can login on the day he joins duties - "Enable User After Start Date": (see section 2.3.1/Table 2-2) - A start date is set when a user account is created. This scheduled task enables user accounts for which the start date has passed, and the user status is Disabled Until Start Date. Note here- the user account is in Disabled State until the Start Date.

So OIM provides out of the box feature to ensure users are able to login to their systems on Day One when they join duties. And also ensure security best practice of making sure user accounts are disabled for non-active users. As discussed above, by creating user in Disabled state ensures that such user accounts/entitlements are set in Disabled state.


References



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