Oracle Waveset (formerly Sun Identity Manager) migration to OIM

Oracle Waveset is former Sun Identity Manager.


Migration Oracle Waveset (OW, earlier Sun Identity Manager) to Oracle Identity Manager


Oracle WevSet (OW) (earlier Sun Identity Manager – SIM) is Identity Management product from Sun that Oracle acquired in and renamed as Oracle Waveset (OW). Oracle Identity Manager (OIM) is a provisioning and identity Management product from Thor Xellerate that Oracle acquired and renamed as Oracle Identity Manager (OIM). Oracle Identity Manager is strategic identity provisioning/reconciliation and management software from Oracle . Oracle Waveset (including Connector Server) will slowly merge with Oracle Identity Manager.
This post covers an overview of Oracle Waveset (OW, earlier Sun Identity Manager) to Oracle Identity Manager migration.
1. Oracle Waveset (OW) objects that can be directly mapped to their equivalents in OIM.
1.1 These will be automatically or partially migrated Not too many surprises here. A good portion of OW objects could find direct mappings in OIM. Example of such objects
a) Enterprise Identity Data Objects (e.g. Organization, Role, User, and Resource)
b) Schema Templates and Policy Objects (e.g. IDM Schema Configuration, Email Templates, and Password Policy)
c) Administration and Authorization Objects (e.g. Capabilities and Admin Roles)
d) Business Logic and Process Data Objects (e.g. Process/Object Forms)
Note: Not all features of these objects could be directly mapped to OIM. For Example, dynamic variables in OW Email Templates need to be manually configured in OIM once these templates are automatically migrated. How much these OW features are used in your OW/SIM implementation will determine the amount of automatic translation that could happen.
2. Oracle Waveset (OW) objects with no direct equivalent in OIM.
2.1 There will be a report capturing these objects and they will require manual migration.
2.2 As a general rule of thumb, any customized XPRESS scripting will likely require re-implementation. The migration toolkit will not be able to translate XPRESS logic into SOA composites or OIM adapters or Java code underlying adapters. User Interfaces and Workflows fall into this category.
3. Audit trail / Historical data. These records will not be automatically migrated
As Oracle Waveset and Oracle Identity Manager employ different schema for persistence of audit records, recommendation is to follow a co-existence strategy. In this approach, audit artefacts would be generated from either OW, OIM or both depending on context / need.
4. Identity Connector Framework (ICF) will be leveraged by the migration toolkit. Plan is to build both OW and OIM resource connectors on top of the new Identity Connector Framework (ICF). It’s already available to Oracle Waveset customers as long as they upgrade their installation to 8.1.x. This not only enables them to leverage new features and enjoy updates to the connectors provided by Oracle but also unifies the underlying infrastructure for a seamless transition by the migration toolkit.
Overall, the Oracle Waveset to Oracle Identity Manager migration toolkit by Oracle is a respectable attempt at automating the migration tasks. It pays attention to details regarding product differences and focuses on identifying customizations that require manual effort to migrate. For example, the toolkit takes care of passwords and challenge questions/answers when migrating OW users such that end users won’t need to reset passwords or re-enter their challenge answers in OIM.
On the other hand, no magic tool could solve real life problems in a quick and easy way. (This was one of the lessons taught in Doraemon’s stories).
Oracle Waveset Object TypeList of ObjectsPre- Migration Analysis by Migration ToolkitMigration Effort Considerations
Out-Of-BoxConnectorsAuthoritative source(HR) Connector (e.g. Active Sync Resource AdaptersAutomatedMight require upgrading to OW version 8.1.X
Managed resources ConnectorsAutomatedMight require upgrading to OW version 8.1.X
Task DefinitionsDeferred Task Scanner (Scan user objects for termination tasks)Semi-AutomatedMap to OIM Scheduled Task. Since the termination on mechanism is different between OW and OIM, the “to-be-terminated” user onjects during cutover period need to be manually migrated
CustomizedUser FormsActive Sync Input Form For HR ConnectorSemi-AutomatedMapped to OIM process Forms and Request Data Set Manual migration is required if any OW-Specific features (e.g. validation logic) are used by the customization.
Update user Form to tag user with the future termination on date
Forms to display details for performing manual termination
Task DefinitionsRequire manual migration. These processes are shared with other use cases (e.g updating user profile from HR)
Processes to process updates from HRManualRequire manual migration. Consider enhancing a grace period before hard termination.
Processes to terminate users in both managed and non-managed resourcesManual
RulesCommon Logic Used by customized user Forms and WorkflowManualRequire manual migration.
Mapped to OIM Email templates. Manual migration is required if any OW-specific features(e.g. Dunamis)
Email TemplatesTermination Email notificationsSemi-Automated


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 machine,  VMware Workstation or VirtualBox. (vmdk format was originally developed by VMware and is an open format now). All of
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

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