Oracle Identity Manager

From Wikipedia, the free encyclopedia
Jump to: navigation, search

Oracle Identity Manager

In computing, Oracle Identity Manager (OIM[1]) enables enterprises to manage the entire user life-cycle across all enterprise resources both within and beyond a firewall. Within Oracle Identity Management it provides a mechanism for implementing the user-management aspects of a corporate policy.[citation needed] It can also audit users and their access privileges.[citation needed]

Versions[edit]

Oracle Identity Manager has evolved based on the needs of enterprise users.[citation needed] It was earlier a Thor Technologies product - after Oracle Corporation acquired Thor (2005), OIM 9i was released. OIM 9i was based on the Struts framework.

Later Oracle Corporation released OIM 11g R1 based on Oracle Application Development Framework. In July 2012 Oracle released OIM 11g R2.

Components[edit]

  • IT Resource Type Def: used to define the connection details of a target system.
  • IT Resource: stores actual connection data. (Password is always encrypted.)
  • Resource Object: the logical representation of the target system.
  • Process Definition: defines the flow of actual tasks.
  • Process Form: table within OIM database to hold data for a given resource object.
  • Process Task: different task associated with a target system.

There are five different types of adapters used for different tasks as listed below:

  1. Process Task Adapter
  2. Pre Populate Adapter
  3. Task Assignment Adapter
  4. Rule Generator Adapter
  5. Entity Adapter

See also[edit]

References[edit]

  1. ^ Thakker, Tushar (2015). "13: Managing Fusion Applications Security". Pro Oracle Fusion Applications: Installation and Administration. Apress. p. 442. ISBN 9781484209837. Retrieved 2017-03-01. Oracle Identity Manager (OIM) manages the identity information and allows us to provision Users and Roles using a simple graphical interface. OIM maintains its own database for storing the identity information and it should be synchronized with LDAP [...].