Showing posts with label UMX. Show all posts
Showing posts with label UMX. Show all posts

Thursday, June 19, 2008

Want to Add a Responsibility? How about Oracle User Management?

When you think of adding a new responsibility to an existing E-Business Suite user, does System Administrator come to mind? Visions of going to the Define User form, tabbing down and finding the new responsibility to add? Did you know that you can add responsibilities to a user through Oracle User Management? Let’s step through how this can happen together. Below I have setup a brand new user without any responsibilities.















Further evidence that there are no responsibilities tied to this user is in the screenshot below where I have logged into this new userid – notice there are no responsibilities listed.













Next, let’s login into the Oracle User Management responsibility and query up the new user “BOYWONDER” where we see again that there are no roles nor responsibilities assigned to this user:












Now let’s go find the US Super HRMS Manager responsibility and assign that responsibility to BOYWONDER as follows:











Now let’s re-query up BOYWONDER to see that the US Super HRMS Manager responsibility has been added in Oracle User Management as follows:












Now, let’s switch over to System Administrator and requery up BOYWONDER to see if the responsibility shows there:
















As you can see, the responsibility has been added through Oracle User Management just as if it had been added through the System Administrator responsibility. Lastly, let’s log back into BOYWONDER and see if he is now a Super HRMS Manager for the US:











And there you have it – BOYWONDER is now an HRMS super hero in good standing. System Administrator? Who needs it – there’s a new super hero in town!


















































Tuesday, April 29, 2008

New Feature for Release 12 – “Manage Proxies”






Ever wanted to get even with those pesky auditors that are always making life more difficult than it has to be just to achieve some level of controlled nirvana? Well, I have just the prescription in the form of a new feature in Release 12 called “Manage Proxies” – this new feature is guaranteed to send the auditors into counseling! This new powerful feature allows Release 12 users to designate a proxy user which can then assume, takeover, inherit, (insert your favorite verb here ______) all, yes ALL, the accesses possessed by the granting user. According to the Release Control Document for Release 12, the rationale behind adding this feature is to allow administrative assistants the ability to manage approvals for their too busy executives; however, there are other ways to accomplish this within the Approvals Management Engine (AME) that doesn’t bring all the controls baggage with it like the “Manage Proxies” function does. To setup a proxy user, all it takes is the assignment of the “Manage Proxies” role which then causes the “Manage Proxies” selection to appear when Preferences are selected from the granting user’s home page (see below). Clicking on the “Manage Proxies” link takes the granting user to a page where one or more proxy users can be added.























Once the “apply” button is hit, then auditor heartburn occurs! The next time the proxy user(s) logs in he/she has “Switch User” displayed in the upper right hand corner of their home page as shown below.









All the proxy user has to do is “Switch User” and bingo, the proxy user now has all the responsibilities from the granting user and can masquerade as that user until the proxy is revoked by the granting user which is shown below.

Of course the proxy user can exercise a very deep philosophical action called “Return to Self” which reverts the proxy user to their original list of responsibilities, but until self actualization occurs, Release 12 schizophrenia exists in all its glory! The only problem is that the mental health hit is not realized by the proxy user nor the granting user – but the poor auditor which discovers this new feature in Release 12 called “Manage Proxies” – enjoy and don’t say you weren’t warned!!!!

Wednesday, February 20, 2008

Role Based Access Control (RBAC), Oracle User Management (UMX) and Release 12



There are three dynamics that come together in Release 12 to produce inflection points where increased levels of access may not have adequate enough controls surrounding them. First and foremost is the emergence of OAFramework applications within the Release 12 footprint which is depicted in the chart to the left.



One of the reasons this is so important is that OAFramework applications look to Oracle User Management (UMX) roles for their security framework which means ever increasing levels of access are being granted through UMX roles rather than through traditional system administration responsibilities and menus. An example of one of these inflection points is in Oracle Cash Management where bank accounts are assigned to Legal Entities through the granting of a specific UMX role. In fact, Oracle Cash Management was redeveloped in OAFramework in Release 12 which is probably a template that Oracle will follow for other applications in future releases.

This emergence of OAFramework challenges our traditional ways to audit the various access levels across the Release 12 footprint. As we all know, Oracle designs “great privilege” into their base deliverables as evidenced by the Payables Manager responsibility and the General Ledger Super User responsibility. “Great privilege” is the second dynamic that is submitted for your consideration. I trust nobody is using the out-of-the-box responsibilities in their production environments, but if “great privilege” is designed into traditional system administration access levels, what about the OAFramework/UMX roles?

Couple “great privilege” with our third dynamic, “inheritance” and you have just poured fuel on the roaring controls fire we’ve been building. “Inheritance” is where a new person inherits all application accesses from another person who has been performing the same role for some period of time. Usually inheritance is a good thing, but in this case, the new AP clerk just inherited all accesses from the other AP clerk who may have been working at that company for 20 years. So, in one simple authorization, the new AP clerk now has 20 years worth of accesses which may or may not be understood, intended nor authorized.

So, let’s recap, there are three dynamics at play here (1) emergence of OAFramework and UMX roles, (2) “great privilege” being designed by Oracle and (3) the ease of “inheritance” which erodes individual authorizations across the Release 12 footprint. Role Based Access Control (RBAC) can mitigate these three dynamics if adopted and designed appropriately. In our next post, we will take a deeper look at RBAC to understand what it is and how it can be designed and deployed at your company to effectively mitigate the new controls inflection points created in Release 12 where traditional system administration meets the emergence of OAFramework and UMX.