Introduction This post is part of a larger series on Oracle Access Manager 11g called Oracle Access Manager Academy. An index to the entire series with links to...
Introduction This post is part of a larger series on Oracle Access Manager 11g called Oracle Access Manager Academy. An index to the entire series with links to each of the separate posts is available. This is the first post of a three part series that expands on a great article Matt wrote --- “The (Windows) Natives Are Restless”. Matt’s article covered some configurations, browser settings, and some examples of role mapping, but I want to dive into this whole WNA solution a...
Introduction This post is part of a larger series on Oracle Access Manager 11g called Oracle Access Manager Academy. An index to the entire series with links to each of the separate posts...
Introduction In Fusion Applications, users are not directly assigned access to individual functions and data. Instead, access is provided through roles. Roles...
Introduction In Fusion Applications, users are not directly assigned access to individual functions and data. Instead, access is provided through roles. Roles group users for a specific purpose and define their access privileges. During the provisioning and installation of Fusion Application, a Super User (FAADMIN, by default) is setup with the following roles, to administer the underlying technical stack (Fusion Middleware) and to act as a Functional Setup Manager....
Introduction In Fusion Applications, users are not directly assigned access to individual functions and data. Instead, access is provided through roles. Roles group users for a specific purpose and...
Introduction This is the second post of a two-post series about pre-populating requests in OIM 11g R2. The first post is available here. This post is also part...
Introduction This is the second post of a two-post series about pre-populating requests in OIM 11g R2. The first post is available here. This post is also part of OIM 11g Academy Series. The approach describe in this post is more sophisticated when compared to the pre-populate plug-in described in Part - 1 of this post. Main Article The emphasis here is UI interaction. It is also important to mention that this approach does not work for requests created through the APIs, it...
Introduction This is the second post of a two-post series about pre-populating requests in OIM 11g R2. The first post is available here. This post is also part of OIM 11g Academy Series. The approach...
Introduction This is the first of a two posts series about pre-populating requests in OIM 11 R2. This post is also part of the OIM 11g Academy Series (Need to...
Introduction This is the first of a two posts series about pre-populating requests in OIM 11 R2. This post is also part of the OIM 11g Academy Series (Need to find this HTTP link). Main Article With the introduction of the Catalog, request creation process changed from a wizard to a shopping cart experience style. But request pre-populating is still a common requirement for OIM customers. There are two different approaches to pre-populate a request: Pre-populate plug-ins ...
Introduction This is the first of a two posts series about pre-populating requests in OIM 11 R2. This post is also part of the OIM 11g Academy Series (Need to find this HTTP link). Main Article With...
Introduction A split profile, or split directory configuration, is one where identity data is stored in multiple directories. A split profile is used to store...
Introduction A split profile, or split directory configuration, is one where identity data is stored in multiple directories. A split profile is used to store custom attributes required for Fusion Application Deployment. This type of deployment is used when you do not want to modify the existing Identity Store by extending the schema. In that case, deploy a new Oracle Internet Directory instance to store the extended attributes. Another multidirectory scenario is one where...
Introduction A split profile, or split directory configuration, is one where identity data is stored in multiple directories. A split profile is used to store custom attributes required for Fusion...
Since the first 11g release, OIM engineering and product management teams have been working hard on field enablement. As part of this work, they created a...
Since the first 11g release, OIM engineering and product management teams have been working hard on field enablement. As part of this work, they created a wonderful set of reusable OIM customizations examples. Such components are called 'OIM assets'. Among these great assets, you can find examples of approval workflow, event handler, scheduled task, UI customization, and others. They can be used as learning assets; and they can be easily modified and deployed to your OIM...
Since the first 11g release, OIM engineering and product management teams have been working hard on field enablement. As part of this work, they created a wonderful set of reusable OIM...
Introduction OIM 11g R2 being such a comprehensive provisioning solution, it provides API’s for almost every aspect of functionality available in the product....
Introduction OIM 11g R2 being such a comprehensive provisioning solution, it provides API’s for almost every aspect of functionality available in the product. This makes it a little difficult to decide which examples are needed the most in the documentation. Fortunately, the documentation does supply samples that can definitely serve as a foundation for more complex pieces of code. Some of the API’s I found developers using more often than others are the ones related to the...
Introduction OIM 11g R2 being such a comprehensive provisioning solution, it provides API’s for almost every aspect of functionality available in the product. This makes it a little difficult to...
Introduction A common requirement in an OIM implementation is to not expose OIM user interface to all types of end users. To address this requirement, usually a...
Introduction A common requirement in an OIM implementation is to not expose OIM user interface to all types of end users. To address this requirement, usually a custom application using OIM APIs is developed and deployed. Such application will expose specific OIM functionalities to end users. In most of the cases, customers want the custom application/OIM APIs to act as the end user, and not as a service account; this approach leverages OIM security model, and the actions...
Introduction A common requirement in an OIM implementation is to not expose OIM user interface to all types of end users. To address this requirement, usually a custom application using OIM APIs...
Introduction OIM 11g R2 provides OIM Developers with the means to implement very sophisticated and functional rich customization to the Out-of-the-Box User...
Introduction OIM 11g R2 provides OIM Developers with the means to implement very sophisticated and functional rich customization to the Out-of-the-Box User Interface. These customizations are capable of surviving the installation of patches, which means that when the OIM installation is patched, the UI customizations don’t have to be re-applied. The customizations are stored as metatada in MDS (Meta Data Store), and it is applied on top of the standard user interface at...
Introduction OIM 11g R2 provides OIM Developers with the means to implement very sophisticated and functional rich customization to the Out-of-the-Box User Interface. These customizations are...
