Security Governance - Governance, Risk, and Compliance Topic for Oracle Applications - page 113

Using this definition of responsibility, it was often necessary to create several similar
responsibilities in order to effectively carve out data and functional security access
for a group of users. This has increased the overall cost of ownership as the number
of responsibilities has grown."
This means that both the vagaries of the delivered responsibilities and the need to
have roles that span distinct sets of data to it are catered for.
Role provisioning
UMX also has the capability to request a role using Oracle Workflow.
The following is the Role Request UI through which users can request roles in a
self-service manner:
Oracle User Management supports three types of registration processes:
• Self-Service Account Requests : If you have ever made an online transaction,
you probably did a self-registration and created an account to tie the order to
your account. This registration process type is very similar in that the system
provides a method for persons to request a new user account. This type of
registration process also offers identity verification, which confirms the identity
of the requester (via an e-mail notification that requires a response) before
the registration request is processed. If the recipient does not reply within a
predetermined amount of time, the request will be automatically rejected.
• Requests for Additional Access : Oracle UMX provides an Access Request
Tool that enables existing users to request additional roles. Users can only
request the additional roles that have been defined as appropriate based on
their current roles. Users can request additional access through the Oracle
User Management Access Request Tool (ART), available in the Global
Preferences menu.