Identity and Access management

Push agent on Target Host: On the target login as root and run the following commands:                             visudo Change Defaults !visiblepw to Defaults visiblepw. Change Defaults requiretty to Defaults !requiretty.(Changes directly can be made to /etc/suoders file with root user) Add oracle ALL=(ALL) ALL Log in to Enterprise Manager as an ADMIN user. Select Setup ->Add Target->Add Target Manually. Select the Add Host Targets option and click Add Host. Add the host names and select the platform. Click Next. Provide the Agent Install Location, click in the Instance directory field to auto-generate the path, create a named credential for the agent user (provide access to root user either by using sudo or pbrun), and clear the value in the port field (this will enable automatic selection of the port), click Next. Review all entered values, and click Deploy Agent. Agent is deployed on the target. Discover Oracle WebLogic Domain Log i

EUS set up for OVD 11.1.1.7 and Novell eDirectory 8.8 SP8 Prerequisites: Ø   Oracle Virtual Directory version 11.1.1.7 is already installed and running. Ø   Novell eDirectory server Version 8.8 SP8 is already installed and running. Ø   iManager version 2.7.7 is already installed. Password management plugin is downloaded and installed on iManager. RBS configuration wizard has run. Ø   Oracle Database (Version 11.2.0.1.0) is already installed and running.  Configuring Novell eDirectory server for EUS Integration For EUS integration a universal password policy has to be implemented on eDirectory and Admin should have access to retrieve the password of the user.   For setting up the universal password policy login to iManager with Admin credentials. Go to ‘Roles and Tasks’ tab and click Passwords. Click Password policies. Click New to create new password policy. Provide the container name, policy name, description and password change message.

With Oracle Virtual Directory a LDAP adapter can be created which is mapped to either user container ("cn=users,dc=example,dc=com") or root value in LDAP server. It can also be mapped to the tree of the server (dc=example,dc=com). If two different LDAP adapters are created within OVD a user can be searched from both the directories or from a single directory based on the Mapped name space in the OVD. Below is the use case scenarios depicting the same: Create an Adapter with OID/OUD using remote base as “” and mapped name space to “dc=eus,dc= oracle ,dc=com”. It can also be mapped to either tree (dc= oracle ,dc=com) or user container (cn=Users,dc= oracle ,dc=com).If we have to search the root values also from OID/OUD then map it to "". Now from the adapter browser even cn=”changelog” can be seen which doesn’t come under “dc=us,dc= oracle ,dc=com” tree in OUD. Create another adapter for Active directory mapping it to remote base as “dc=dev,dc=