Chuyển đến nội dung chính

Approval specific web services in Oracle IDM

Source: https://abhirockzz.wordpress.com
Oracle IDM integrates with and leverages the SOA suite for approval related features (SOA is quite rich to be honest and is utilized as the back bone for Web Services connector as well). SOA is not just for namesake – SOA suite does in fact rely on the concept of loosely coupled and independent services.

The approval engine makes use of three such web services

  • Request web service: this is deployed on the OIM server
  • Request Callback web service: this is deployed on SOA server
  • Provisioning Callback web service: this too is deployed on OIM and used in context of approvals related to Disconnected application instances

But how/when are these (SOA) services leveraged ?

Consider an example of a basic approval process
  • OIM approval engine calls a SOA composite (from within an approval policy) in response to evaluation of a self service request. The internals of this call are out of scope of this post (maybe some other time!)
  • Operations within the SOA composite are executed and here is where the Request Callback web service comes in to play. The SOA composite calls the Request Callback web service and appraises it of the result of the SOA composite execution (approval/rejection)
  • The Request Callback web service calls relays the result back to approval/request engine within OIM which then proceeds accordingly
Request Callback Web Service
Request Callback Web Service

So what is the Request web service all about ?

This is a generic purpose web service available OOTB in OIM (all you need to do is deploy it). It exposes information within OIM such as users, catalog, organizations etc. You can leverage it within SOA composite (just a few click!) to make your life easier (its not mandatory, but you might need to use this more often than not in order to make dynamic decision making)

Provisioning Callback web service

This is used by the OOTB SOA composite (for disconnected applications) to relay the approval decision back to OIM provisioning engine so that it can mark the task as completed and hence the disconnected instance would show up as Provisioned (this of course is the OOTB behavior which is subject to customization if needed)
Provisioning Callback Web Service
Provisioning Callback Web Service

Nhận xét

Đăng nhận xét

Bài đăng phổ biến từ blog này

Oracle IDM Auditing

Source: https://abhirockzz.wordpress.com Reporting  is a vital functionality in any product which deals with sensitive information. Same applies to Identity & Access Management tools. Oracle IDM’s Auditing module acts as a foundation for its OOTB Reporting capabilities. Let’s take a quick look at  Auditing engine  and how it facilitates the Reporting functionality within OIM The use case presented here is simple –  change to a user record in OIM. What are the sequence of events which get triggered from an Audit perspective? This is best explained by a diagram. I came up with the  figure below  in an attempt to better articulate the process. Although the diagram is self explanatory, a theoretical translation of the same is not going to harm us!  The updated/created user record gets pushed into the  USR  table (stores the user information) – Its a normal process by which the information gets recorded in the OIM Database The information is further propagated by the  OI

Allow Duplicate Emails

Version: Oracle Identity Manager 11.1.2.3.0 Step 1:  Login to Oracle Identity System Administration Step 2: On the navigation menu, select Configuration Properties under System Configuration. Step 3: Create the following System Property. Step 4: Verify using duplicate emails.