Category: <span>oracle</span>

While we all do our best to avoid it, occasionally a situation occurs where a user’s Account Name does not match the actual account name on the target account, or the username. Typically this will occur due to peculiarities in your Oracle Identity Manager configuration. Should you find yourself in this situation (as one of our

The simpler functions used to control user life cycle in Oracle Identity Manager 11g, like start and end date, are also some of the most useful. Using Start Date During user creation, OIM evaluates the “Start Date” attribute. If the attribute is set to the current day or before (or left blank), the user is

There are times when a policy is more effective when returning a piece of information back to the end user.   To setup the basis for obligation we will cover the basics of OES Authorization policy.  When modeling policy in OES they are split up as either static or dynamic.   Policy also takes on behaviors of

During a PeopleSoft SSO project using OAM, we came across an issue that there was not a lot of information on. When using PeopleSoft at our customer, they need to allow access for a particular group of users directly into PeopleSoft for administration / testing. This is normally fine and would just add the users

I recently encountered an issue at a client that I thought might be useful to share with others. We were implementing OAM 11.1.2.2 using the F5 (v11.5.2) OAM APM module to act as the webgate in our test environment. Our initial implementation used Open security mode to validate the connection worked. We then progressed to

IDMWORKS Recognized for Expertise in Selling, Deploying and Supporting Oracle Identity and Access Management Solutions August 12, 2015 – IDMWORKS today announced that it has achieved Platinum partner status in Oracle PartnerNetwork (OPN). By attaining Platinum level membership, Oracle has recognized IDMWORKS for its in-depth expertise and excellence in delivering identity and access management solutions

So I ran into an issue with OAM 11gR2PS2 where I needed to modify the retry limit for the authentication scheme.  Previous versions of OAM used a system level value that you could define in oam-config.xml (per https://support.oracle.com/epmos/faces/DocumentDisplay?id=1360866.1).  When I tried that for PS2, I still saw the default 5 retries. I then stumbled onto an

Oracle introduced their Mobile Security Suite last year and over the past few months we’ve had a chance to work with this exciting new product. One key piece of this product is the containerization tool, which containerizes and signs app to enable the secure tunnel, authentication through the secure container, encryption, etc. Recently we had

OIM ships with an out of the box capability to purge Recon events. Starting with R2 PS2, this feature is available via a scheduled job called OIM Data Purge Task. Recently we experienced a strange issue where not all eligible recon events were getting purged. Specifically, the reconciliation purge retention period was set to 7