This post is the fourth and last post of a series by Andre Correa and Paulo Pereira on OAG (Oracle API Gateway).
In the first post we introduced the use case and talked about the Kerberos authentication part.
In the second post we talked about Role Based Access Control.
In the third post, we described how to propagate the authenticated user through a SAML token and also covered OWSM configuration in OSB and SOA.
In this post we talk about the client, how we actually submit a Kerberos token along with our request to OAG.
In the first post, we said (verbatim):
“Perhaps the most challenging part was the test client. Supporting Kerberos was a must. Our first and natural attempt was OAG’s API Explorer (formerly OEG Service Explorer). After numerous attempts, configuration changes everywhere, we came to the the conclusion that it simply does not support the SPNEGO protocol properly. In summary, it seems that it doesn’t honor the second leg of the protocol, i.e., after receiving a “WWW-Authenticate: Negotiate” HTTP header in the response, it does not resubmit the request along with the Kerberos token. And we also did not find a way to bypass SPNEGO and submit the Kerberos token directly. The free version of SOAP UI also failed.
Fortunately, via Prasad’s blog post, we came to know a .Net-based tool called WCFStorm-lite, dead simple, that just works. However, another requirement for this exercise was to show test automation best practices. So the client tool should ideally have scripts capabilities, allowing for the client integration into an ANT build script, for example. WCFStorm-lite has some scripts capabilities, but we did not go any further in looking at them, because almost at the same time we got to know Apache CXF’s support for Kerberos.
That basically put an end to our research. What could be better than simply writing a piece of java code? At the heart of Apache CXF’s framework are what they call interceptors, which are basically web services handlers. An inbound interceptor is attached to a web service and processes the message before service invocation. An outbound interceptor is attached to a web service proxy and process the message as it leaves the client. An out-of-the-box Kerberos interceptor interfaces with the KDC, gets a Kerberos token and attaches it to the request before sending it out to the web service (in our use case, a web service exposed by OAG).”
Very well, let’s talk about how to configure a Kerberos Outbound Interceptor in Apache CXF.
Friday, June 14, 2013
Thursday, June 13, 2013
Part 3: Kerberos Authentication, RBAC and SAML identity propagation in OAG
This post is the third one of a series by Andre Correa and Paulo Pereira on OAG (Oracle API Gateway).
In the first post we introduced the use case and talked about the Kerberos authentication part.
In the second post we talked about Role Based Access Control.
In this one we describe how to build a SAML token out of the authenticated user and sign it so it properly interoperates with an OWSM server-side policy applied to OSB proxy service. We also cover the necessary OWSM configuration in OSB and SOA. As a reminder, a typical request in our exercise flows through OTD -> OAG -> OTD -> OSB -> OTD -> SOA -> Stub server, and we're required to keep the user identity all the way up to the Stub server.
Now we're specifically talking about the third policy in our overall circuit:
'Add SAML token policy' is as simple as:
We first add the SAML token (using the Insert SAML Authentication Assertion filter), then we sign it (using the XML Signature Generation filter). Let's look at each filter in detail.
Monday, June 3, 2013
OIM 11g R2 Performance Patch
Oracle has released a set of patches to address some performance issues in OIM 11g R2 self-service interface. Information about these patches is available in the following Oracle support note:
Any customer who is running OIM or implementing OIM at this point should plan to apply the patches.
Just a reminder, the recommendation is always to start applying patches in lower environments: from DEV to PROD. Don't forget to validate the patches in one environment before proceeding to the next.
- Document 1557879.1 OIM 11gR2: Patches for Performance Issues Related to Self-service UI
Any customer who is running OIM or implementing OIM at this point should plan to apply the patches.
Just a reminder, the recommendation is always to start applying patches in lower environments: from DEV to PROD. Don't forget to validate the patches in one environment before proceeding to the next.
Tuesday, May 7, 2013
OIM 11g R2 Self Registration with CAPTCHA
This post walks you through the fun of customizing OIM and adding a CAPTCHA solution to the self-registration page. Captcha solutions are largely used in web sites to try to prevent automated robots from registering, filling forms, sending messages and many other things.
The captcha solution used is Simple Captcha and it is available here. It is easy to use and easy to hook into applications.
This is another post of the Oracle Identity Manager Academy. To check other tricks, tips and examples you can find the academy post here.
The captcha solution used is Simple Captcha and it is available here. It is easy to use and easy to hook into applications.
This is another post of the Oracle Identity Manager Academy. To check other tricks, tips and examples you can find the academy post here.
Labels:
CAPTCHA,
OIM,
oim 11g academy,
self registration,
UI customization
Wednesday, May 1, 2013
Synchronization of Roles in Catalog OIM 11g R2
Introduction
The Catalog is one of the most fundamental features of OIM
11g R2 request based provisioning. All requests for Resources/Accounts,
Entitlements and Roles are accomplished through the Catalog. Roles in OIM 11g
R2 can be defined within a given category. There are two main out-of-the-box
categories: OIM Roles and Default. The category affects the visibility of the
Role in the Catalog.
Sometimes, customers may require to change the category of
an existing Role in order to make it possible to request the Role through the
Catalog. If the Role was initially created within the OIM Roles category, it will not be visible in the Catalog because
there is no entry in the Catalog's table for the Role.
Procedure
A Role is available in the Catalog when its category is set
to 'Default'. This can be ensured by modifying the Role's attributes in the
Self-Service User Interface and selecting the 'Default' category from the List
of Values. The picture that follows shows where this is done and provides an
example:
In the example above, the role MASSACHUSETTS ORG MEMBER was
originally created with OIM Roles as the selected category. As a result, this
role can't be requested through the Catalog. The role's category will need to
be updated to 'Default'. The images below demonstrate the change:
Roles are published immediately after they are created;
however, if a Role is updated after creation like in the previous example, the
Catalog Synchronization Job has to be executed to reflect the changes in the
Catalog.
To invoke the Catalog Synchronization Job, an Administrator
needs to log in to the System Administration Console of OIM and open the
Scheduler Window; then navigate to the Catalog Synchronization Job as shown in
the following picture:
The Job must be executed with the following values in the
Job's attributes:
- Mode = full
- Process Roles set to Yes
- Updated Date must be blank
After the execution of the Catalog Synchronization Job,
searching for the Role in the Catalog should now display the role in the
results as shown below:
Summary
The Catalog is one of the main components of OIM 11g R2. The
Request-Based provisioning functionality revolves around it. Any entity in OIM
that can be requested by users needs to be visible in the Catalog. Roles that
have OIM Roles as their category, are not visible in the Catalog; only the ones
in the 'Default' category will be displayed in Catalog Search Results.
If a Role was initially created with OIM Roles as its
category and then is updated to the Default category will not be displayed in
the results of a Catalog search unless the Role is added to the CATALOG table
in OIM's Database. This is accomplished by running the Catalog Synchronization
Job through OIM's Scheduler. The job must be executed in Full mode, the
'Process Roles' option must be set to 'Yes' and the 'Updated Date' value must
be blank.
Subscribe to:
Posts (Atom)



