How to Configuring an OID Authentication Provider in WebLogic 10.3.6

Ans :   Configuring an OID Authentication Provider in WebLogic 10.3.6

-----------------------------------------------------------------------------------------

This is the architecture that depicts the configuration of an OID LDAP-based authentication provider used by OPSS applications deployed on a WebLogic Server environment. 

Follow the steps below to configure an OID authentication provider using the Weblogic Administration Console:

1.	Open the Firefox web browser using the  icon on the launch panel. Make sure the WebLogic Server is running before continuing on to the next step.
2.	Open the WebLogic Administration Console by browsing to http://localhost:7001/console. Login using the following credentials: Username: weblogic Password: welcome1
3.	Click the Security Realms link in the Domain Structure pane to show the list of security realms for the domain.
4.	Click the myrealm link in the Realms pane to show the settings for the domain's security realm.
5.	Click the Providers tab to show the security providers configured for myrealm.
6.	Click the Authentication tab to list the currently configured authentication providers for this domain's security realm. The default out-of-the-box providers are shown for the embedded LDAP authentication provider and identity asserter. This is where you configure the new OID authentication provider.
7.	Click New to create a new authentication provider for this domain.
8.	The Create a new Authentication Provider page is displayed. Give your new authentication provider a name, such as OID Authenticator, select the type called OracleInternetDirectoryAuthenticator, and click OK.
9.	You should now see your new OID authenticator in the list of authentication providers, at the bottom of the list.
10.	Click the link for your OID authentication provider to configure its settings.
11.	The Settings for OID Authenticator is displayed. Click the Provider Specific tab to configure the detailed settings for this provider.
12.	This step guides you through all of the settings for configuring your new OID authentication provider. All the settings are made on a single configuration page, however we go through them one section at a time in this instruction. The first section contains the Connection settings for the OID server. Use the values from the table below for this section: Name Value Purpose Host: localhost The OID host name Port: 3060 The standard OID listening port Principal: cn=orcladmin The LDAP user that logs into OID on behalf of your authentication provider Credentials: welcome1 Password for the principal user Confirm Credentials: welcome1 Confirmation of the password SSL Enabled: Unchecked Enables or disables SSL connectivity Validate your settings against the screen shot below: The next section contains the Users settings for the OID provider. Use the values from the table below for this section: Name Value Purpose User Base DN: cn=Users,dc=us,dc=oracle,dc=com The root (base DN) of the LDAP tree where searches are performed for user data All Users Filter: Leave as default The LDAP search filter that is used to show all the users below the User Base DN User From Name Filter: Leave as default The LDAP search filter used to find the LDAP user by name User Search Scope: Leave as default Specifies how deep in the LDAP tree to search for users User Name Attribute: Leave as default The attribute of the LDAP user that specifies the user name User Object Class: Leave as default The LDAP object class that stores users Use Retrieved User Name as Principal: Checked Specifies if the user name retrieved from the LDAP directory will be used as the Principal in the Subject Validate your settings against the screen shot below: The next section contains the Groups settings for the OID provider. Use the values from the table below for this section: Name Value Purpose Group Base DN: cn=Groups,dc=us,dc=oracle,dc=com The root (base DN) of the LDAP tree where searches are performed for group data All Groups Filter: Leave as default The LDAP search filter that is used to show all the groups below the Group Base DN Group From Name Filter: Leave as default The LDAP search filter used to find the LDAP group by name Group Search Scope: Leave as default Specifies how deep in the LDAP tree to search for groups Group Membership Searching: Leave as default Specifies whether group searches into nested groups are limited or unlimited Max Group Membership Search Level: Leave as default Specifies how many levels of group membership can be searched. This setting is only valid if GroupMembershipSearching is set to limited Ignore Duplicate Membership: Unchecked Determines whether duplicates members are ignored when adding groups. Validate your settings against the screen shot below: Click Save to persist your changes.
13.	Click the Common tab in the Settings for OID Authenticator pane to show settings common to all authentication providers.
14.	Change the Control Flag setting to SUFFICIENT and click Save. This setting allows this provider to participate in the authentication process without requiring the user to be in its identity store.
15.	Click the Providers link the breadcrumb displayed near the top of the page to quickly navigate back to theAuthentication Providers page.
16.	Click the DefaultAuthenticator link to display its common settings so you can change its control flag toSUFFICIENT as well.
17.	Change the Control Flag setting to SUFFICIENT and click Save. This setting allows this provider to participate in the authentication process without requiring the user to be in its identity store.
18.	Click the Providers link the breadcrumb displayed near the top of the page to quickly navigate back to theAuthentication Providers page.
19.	Click Reorder to change the order of your configured authentication providers. If you remember from the OPSS Concepts self-study course, OPSS obtains its authentication configuration from the authentication provider configuration found in the WebLogic Server domain. It also states that OPSS first looks at all of the LDAP-based authentication providers in the list, and chooses the first one in the list with the highest control flag setting. Because we configured both LDAP-based authentication providers to use the SUFFICIENTcontrol flag setting, OPSS would use the default authenticator if we left the configuration as it is now. In order to ensure that OPSS recognizes your new OID authenticator as its authentication provider, you must reorder your list of authentication providers so that the OID authentication provider is first in the list.
20.	Select the OID Authenticator and use the arrows on the right to move it into the first position. Click OK.

Oracle identity Manager CustomConnector for OracleDatabase ( MobileApplication )

/*
Source Code :

OracleDBApplication.java
-----------------------------
*/


package com.luckyfusion.customdbconnector;

import java.sql.Connection;
import java.sql.DriverManager;
import java.sql.PreparedStatement;
import java.sql.SQLException;
import java.util.Properties;

/**
 * @author Lakshmi Prasad Reddy
 *
 */
public class OracleDBApplication {

/**
* @param args
*/

public static void main(String[] args) {



// TODO Auto-generated method stub


/***
* Properties connectionProps = new Properties();
        connectionProps.setProperty("user", "mobileadmin");
        connectionProps.setProperty("password", "oimdb");
     
        String jdbcUrl = "jdbc:oracle:thin:@" +"192.168.1.100" +":" +"1521" +":"+"oimdb";
        System.out.println("JDBC URL :: " + jdbcUrl);
        String jdbcDriver = "oracle.jdbc.driver.OracleDriver";

OracleDBApplication oDbApp = new OracleDBApplication();
   oDbApp.createUser("192.168.1.100", "1521", "oimdb", "mobileadmin", "oimdb", jdbcDriver, "Lakshmi", "Prasad", "lucky", "1149", "LREDDY", "IN", "IDM", "LuckyFusion");
oDbApp.modifyUser("192.168.1.100", "1521", "oimdb", "mobileadmin", "oimdb", jdbcDriver, "YYY", "EMAIL", "YTR", "CCC");
oDbApp.deleteUser("192.168.1.100", "1521", "oimdb", "mobileadmin", "oimdb", jdbcDriver, "MOBILEDATA", "USERID", "USERID");
*
*
*
*/



}

// Get Oracle Database connector Connection


public Connection getDatabaseConnection(String url, Properties properties, String jdbcDriver)

{
System.out.println("Entering getConnectionWithTimeout");

        Connection connection = null;
     
try {
        Class.forName(jdbcDriver);
connection = DriverManager.getConnection(url,properties);
System.out.println("Connection :: " + connection);
  }

catch (SQLException e)
{
System.out.println("Error ::  Error while creating the connection with database :: " + e.getMessage());
e.printStackTrace();
}

catch (ClassNotFoundException e)
{
System.out.println("Error ::  Error while creating the connection with database :: " + e.getMessage());
e.printStackTrace();
}
     
System.out.println("Exiting getConnectionWithTimeout");
        return connection;
    }



// Create an User

public String createUser(String serverAddress,String portNumber,String sid,String dbAdminID,String dbAdminPassword,String jdbcDriver,String userID,String firstName,String lastName,String mobileNumber,String manager,
String country,String company,String email)
{
System.out.println("\n\n*********** Entering createUser ***************");
System.out.println("User ID :: " + userID + " First Name :: " + firstName + " Last Name :: " + lastName +" Email :: " + email);
System.out.println("Manager :: " + manager + " Country :: " + country + " Company :: " + company +" Mobile :: " + mobileNumber);

String taskResponse = "NOT_COMPLETED"; // It's the default response
String insertQuery = "INSERT INTO MOBILEDATA (USERID, FIRSTNAME, LASTNAME, EMAIL, MOBILENUMBER, MANAGER, COUNTRY, COMPANY) VALUES (?,?,?,?,?,?,?,?)";

Connection connection = null;
Properties connectionProps = new Properties();
    connectionProps.setProperty("user",dbAdminID);
    connectionProps.setProperty("password",dbAdminPassword);
 
    String jdbcUrl = "jdbc:oracle:thin:@" +serverAddress +":" +portNumber +":"+sid;
    System.out.println("JDBC URL :: " + jdbcUrl);
 
    connection = getDatabaseConnection(jdbcUrl, connectionProps, jdbcDriver);
    if(connection != null){
    try

{
   
   
    // JDBC CODE SAMPLE: http://www.mkyong.com/jdbc/jdbc-preparestatement-example-insert-a-record/
   
   
   
PreparedStatement preparedStatement = connection.prepareStatement(insertQuery);
preparedStatement.setString(1, userID);
preparedStatement.setString(2, firstName);
preparedStatement.setString(3, lastName);
preparedStatement.setString(4, email);
preparedStatement.setString(5, mobileNumber);
preparedStatement.setString(6, manager);
preparedStatement.setString(7, country);
preparedStatement.setString(8, company);
int count = preparedStatement.executeUpdate(); // It returns how many records are inserted

if(count == 1)
{
taskResponse = "CREATE_SUCCESS";
}
else
{
taskResponse = "CREATION_FAILURE";
}

   }

catch (SQLException e)

{
taskResponse = "CREATION_FAILURE";
System.out.println("Error :: While creating the user" );
e.printStackTrace();
}


    }

else {
    taskResponse = "NULL_CONNECTION";
    }
 
    System.out.println("\n\n*********** Exiting createUser ***************");
return taskResponse;
}


// Update or Modify an user


public String modifyUser(String serverAddress, String portNumber, String sid, String dbAdminID, String dbAdminPassword, String jdbcDriver, String userID, String fieldName, String fieldValueNew, String fieldValueOld){
System.out.println("\n\n*********** Entering modifyUser ***************");
System.out.println("User ID :: " + userID + " Field Name :: " + fieldName + " Field Value (New) :: " + fieldValueNew +" Field Value (Old) :: " + fieldValueOld);

String taskResponse = "NOT_COMPLETED"; // It's the default response
String updateQuery = "UPDATE MOBILEDATA SET ? = ? WHERE USERID = ?";
Connection connection = null;
Properties connectionProps = new Properties();
    connectionProps.setProperty("user", dbAdminID);
    connectionProps.setProperty("password", dbAdminPassword);
 
    String jdbcUrl = "jdbc:oracle:thin:@" +serverAddress +":" +portNumber +":"+sid;
    System.out.println("JDBC URL :: " + jdbcUrl);
 
    connection = getDatabaseConnection(jdbcUrl, connectionProps, jdbcDriver);
    if(connection != null){
    try {
    // JDBC CODE SAMPLE: http://www.mkyong.com/jdbc/jdbc-preparestatement-example-insert-a-record/

PreparedStatement preparedStatement = connection.prepareStatement(updateQuery);
preparedStatement.setString(1, fieldName);
preparedStatement.setString(2, fieldValueNew);
preparedStatement.setString(3, userID);
int count = preparedStatement.executeUpdate(); // It returns how many records are inserted
System.out.println("\n*******************************");
System.out.println("\nUser Modified :: " + userID );
System.out.println("\n*******************************");
if(count == 1){
taskResponse = "MODIFY_SUCCESS";
}
else {
taskResponse = "MODIFY_FAILURE";
}

}

catch (SQLException e)
{
taskResponse = "MODIFY_FAILURE";
System.out.println("Error :: While Modifying the user" );
e.printStackTrace();
}

    }

else

{
    taskResponse = "NULL_CONNECTION";
    }
 
    System.out.println("\n\n*********** Exiting modifyUser ***************");
return taskResponse;
}

// Delete an User


public String deleteUser(String serverAddress, String portNumber, String sid, String dbAdminID, String dbAdminPassword, String jdbcDriver, String userID, String tableName,
String userIDColumn){
System.out.println("\n\n*********** Entering Delete User ***************");
System.out.println("User ID :: " + userID );

String taskResponse = "NOT_COMPLETED"; // It's the default response
String insertQuery = "DELETE FROM ? where ? = ?";
Connection connection = null;
Properties connectionProps = new Properties();
    connectionProps.setProperty("user", dbAdminID);
    connectionProps.setProperty("password", dbAdminPassword);
 
    String jdbcUrl = "jdbc:oracle:thin:@" +serverAddress +":" +portNumber +":"+sid;
    System.out.println("JDBC URL :: " + jdbcUrl);
 
    connection = getDatabaseConnection(jdbcUrl, connectionProps, jdbcDriver);
    if(connection!= null){
    try {
PreparedStatement preparedStatement = connection.prepareStatement(insertQuery);
preparedStatement.setString(1, tableName);
preparedStatement.setString(2, userIDColumn);
preparedStatement.setString(3, userID);
int count = preparedStatement.executeUpdate(); // It returns how many records are inserted
System.out.println("\n*******************************");
System.out.println("\nUser Got Deleted :: " + userID);
System.out.println("\n*******************************");
if(count == 1){
taskResponse = "DELETE_SUCCESS";
} else {
taskResponse = "DELETE_FAILURE";
}

} catch (SQLException e) {
taskResponse = "DELETE_FAILURE";
System.out.println("Error :: While Deleting the user" );
e.printStackTrace();
}
    } else {
    taskResponse = "NULL_CONNECTION";
    }

    System.out.println("\n\n*********** Exiting Delete User ***************");
return taskResponse;
}


// Enable an User

// Disable an User

// Lock an User

// Unlock an User

// Search User

}


Thanks & Regards

Lakshmi Reddy N

OIM Account Restore User Status From Deleted to Active

 OIM Account Restore User Status From Deleted to Active

Restoring the Deleted Account in OIM

When you delete the user from the Oracle Identity Manager System, the user will not been removed physically from the system and also it changes the status from Active to Deleted. It also revoke the resources from the target system for the deleted user.

I need to reactivate the deleted user from the Oracle Identity Manager as follows:

1. Login to the OIM data base user into the data base and update the user status from Deleted to Active.

2. Execute the following sql to update the user status

UPDATE USR SET USR_STATUS = 'Active' WHERE usr_login='login id'

replace login id with your login id.

3. Login to the OIM Admin Console and verify the user status is changed  from Deleted to Active.

4. Re-Provision the users.

Thanks & Regards 

---------------------------

Lakshmi Prasada Reddy Nandyala 

A Tour of Oracle Privileged Account Manager

A Tour of Oracle Privileged Account Manager

Usage management of sensitive accounts of LDAP, Database, Linux or custom applications using Oracle Privileged Account Manager 11gR2PS1

Downloads:

Oracle Identity Management

Overview:

Oracle Privileged Account Manager is a new product added in the Oracle Identity Management 11gR2 release. As its name suggests, it deals with the management of privileged accounts. By the word “privileged account” we mean that these accounts can access the sensitive data in the organization. Following are the examples of the privileged accounts:

• Unix root account
• Database SYSDBA / SYSOPER accounts
• Windows Administrator accounts
• Application accounts which access sensitive information
• System Administrator accounts

Oracle Privileged Account Manager provides an easy to implement and versatile solution for managing high risk accounts. It lets you manage the password policies and the usage policies (e.g. time duration for which you can use the account) for the accounts. It leverages Identity Connector Framework to integrate with third party applications which are supported out of the box. It supports the break the glass facility where one person performs the tasks of another person in case the person is not available due to some emergency. One of the highlighting features is the ability of OPAM to provide comprehensive auditing and reporting of who has acted on a particular account at certain point in time as well as the real time data. It can be combined with Oracle BI Publisher to generate reports. Figure 1 shows the overall architecture of OPAM.

Figure 1

There are two ways in which you can access the Oracle Privileged Account Manager features: Graphical User Interface (GUI) and Command Line Interface (CLI). The latter can be extended to invoke all CLI supported operations through Java API which is given this post. The GUI and CLI interact with the Oracle Privileged Account Manager Server over REST services. The OPAM Server is a component that handles password requests, generates passwords, and protects the password keystore. Figure 2 shows the GUI, CLI and other clients communicate with OPAM using the RESTful interface.

Figure 2

Authentication:

 The authentication framework of the Oracle Privileged Account Manager leverages SAML based token authentication. It can be integrated with Oracle Access Manager Single Sign On. OPAM CLI Supports HTTP Basic Authentication over SSL to connect to OPAM Server.

Authorization:

 There are several Admin Roles supported by OPAM to restrict the sensitive usage of the application:

• Application Configurator – OPAM_APPLICATION_CONFIGURATOR
• Security Administrator – OPAM_SECURITY_ADMIN
• Security Auditor – OPAM_SECURITY_AUDITOR
• User Manager – OPAM_USER_MANAGER

Administration:

1.     Targets:

A target in OPAM is a system which contains users, and relies on users, system, or application accounts. You need to register the target system in order to manage the accounts associated with the target.  Currently as of release 11.1.2.1.0 OPAM supports four types of pre-built targets. You can see the four supported targets in Figure 3.

Figure 3

Generally adding a target involves providing the values of the host, port, domain and other minimum useful information required to retrieve the accounts from the target system. The two targets needs extra attention - The database target is supported for Oracle, MSSQL, MYSQL, DB2 and Sybase. Lockbox allows us to manage a specific target without configuring any connector.

2.     Accounts:

An account represents the privileged account on a target system. OPAM does not create or delete accounts on the target system; it only manages the existing accounts. When a new account is added in OPAM server, only a reference to that account gets created. Deletion of account from OPAM does not delete the account from the target. OPAM enables you to specify whether an account is shared or not shared. Shared accounts enable multiple users to use the account at the same time. Default (unshared) accounts can be used by only one user at a time. Below Figure 4 shows the database accounts containing the word sys in a database target.

Figure 4

3.     Grantee:

Grantees are users or groups that have been granted access to one or more privileged accounts. Users or groups are assigned to a privileged account in the Account tab. As you can see in Figure 5, user.0 is a grantee for the account DEVOAM_OPAM and there is no group specified.

Figure 5

4.     Check out and Check in:

Administrators or end users can check out an account if they have been granted access to that account. When a user checks out an account, by providing a comment, it gets the access to the password of the account. The password is generated based on the Password Policy attached to the privileged account. On successful checking out, unshared accounts become unavailable for other users to check out until the account is checked in again by the user. Checking in of account resets the password of the account. In case of shared accounts, the password is reset only when all the users check in the account. Figure 6 shows that the accounts which are granted to the logged in user are checked in and ready to be checked out.

Figure 6

5.     Password Policies:

The password policies capture the password construction rules enforced by a specific target on an associated privileged account. Every privileged account must have an associated password policy. OPAM provides Default Password Policy. However you can create custom password policies as per your requirements.

6.     Usage Policies:

The usage policies define when and how a privileged account can be used by a grantee. These are applied at the level of a grant. OPAM provides Default Usage Policy. However you can create custom usage policies as per your requirements.

7.     Reports:

The reports provide the real time information about the status of accounts and targets being managed by OPAM. OPAM provides support for 3 types of reports:

• Deployment Reports : View information about how targets and privileged accounts are currently deployed
• Usage Reports : View information about how privileged accounts are currently being used in the deployment
• Failure Reports : View information about current state of target and account failures

8.     ICF Connectors:

Connectors enable OPAM to interact with the third party target systems. OPAM leverages connectors that are compliant with the ICF standard. OPAM can use custom connectors to interact with the target systems other than the traditional LDAP, database and UNIX system. After the connector is developed and ready to be integrated with OPAM, the connector bundle needs to be put in a location where OPAM can access it at runtime. All the connector related configurations are stored in the file ORACLE_HOME/opam/config/opam-config.xml which schematically is governed by ORACLE_HOME/opam/config/opam-config.xsd. If you have made correct <connectorConfig> entries in opam-config.xml, you will see the new target in the Target dropdown after the server is restarted.

Command Line Interface:

Oracle Privileged Account Manager lets you interact with the OPAM server via HTTP Basic Authentication over SSL. You can perform certain tasks via command line which you can do via GUI. CLI can be launched by ORACLE_HOME/opam/bin/opam.sh (UNIX) or ORACLE_HOME/opam/bin/opam.bat (Windows) . Supported commands are - addaccount, addtarget, checkin, checkout, displayallaccounts, displayallgroups, displayalltargets, displayallusers, displaycheckedoutaccounts, displaydomaintree, displaytargettypetree, grantgroupaccess, grantuseraccess, removeaccount, removegroupaccess, removetarget, removeuseraccess, retrieveaccount, retrievegrantees, retrievegroup, retrievetarget, retrieveuser, searchaccount, searchgroup, searchtarget, searchuser, showpassword

Following command shows an example of how to issue addaccount command:

-url https://hostname:sslport/opam -u <username> [-p <password>] [debug] -x addtarget -targetname <targetname> -host <hostname> -port 22 -organization <organization>

Interacting with RESTful Interface:

OPAM Server has exposed certain RESTful interfaces which are consumed by the GUI and also can be incorporated with other applications which provide the ability to consume REST services. Using RESTful interface of OPAM, you can perform several operations on Targets, Accounts, Users, Groups, Password and Usage Policies. Following is the Java code sample showing the basic REST operations that you can perform:

OPAMRestClient.java

package com.mycompany.opam.demo.rest.client;

import java.io.IOException;

import java.io.InputStream;

import java.io.InputStreamReader;

import java.net.MalformedURLException;

import java.net.URL;

import javax.net.ssl.HostnameVerifier;

import javax.net.ssl.HttpsURLConnection;

import javax.net.ssl.SSLSession;

import org.apache.commons.codec.binary.Base64;

/**

 * @author Ganesh

 *

 */

public class OPAMRestClient {

        /**

         * @param args

         */

        public static void main(String[] args) {

                OPAMRestClient client = new OPAMRestClient();

                client.authAndGet();

                client.checkOutAccount();

                client.checkInAccount();

        }

        private void authAndGet() {

                String webPage = "https://192.168.1.31:18102/opam/";

                String result = execute(webPage, "opamadmin", "welcome1", "GET");

                System.out.println("*** RESULT ***");

                System.out.println(result);

        }

        private void checkOutAccount() {

                String webPage = "https://192.168.1.31:18102/opam/account/3a32f71b320645f7b9b594fc8e864089/checkout";

                String result = execute(webPage, "user.0", "welcome1", "PUT");

                System.out.println("*** RESULT ***");

                System.out.println(result);

        }

        private void checkInAccount() {

                String webPage = "https://192.168.1.31:18102/opam/account/3a32f71b320645f7b9b594fc8e864089/checkin";

                String result = execute(webPage, "user.0", "welcome1", "PUT");

                System.out.println("*** RESULT ***");

                System.out.println(result);

        }

        /**

         * @param webPage

         * @return

         * @throws MalformedURLException

         * @throws IOException

         */

        private String execute(String webPage, String name, String password,

                        String requestMethod) {

                String authString = name + ":" + password;

                System.out.println("auth string: " + authString);

                byte[] authEncBytes = Base64.encodeBase64(authString.getBytes());

                String authStringEnc = new String(authEncBytes);

                System.out.println("Base64 encoded auth string: " + authStringEnc);

                URL url;

                HttpsURLConnection httpsCon = null;

                String result = null;

                try {

                        url = new URL(webPage);

                        httpsCon = (HttpsURLConnection) url.openConnection();

                        httpsCon.setRequestMethod(requestMethod);

                        httpsCon.setHostnameVerifier(new HostnameVerifier() {

                                @Override

                                public boolean verify(String hostname, SSLSession session) {

                                        return true;

                                }

                        });

                        httpsCon.setRequestProperty("Authorization", "Basic "

                                        + authStringEnc);

                        httpsCon.connect();

                        InputStream is = httpsCon.getInputStream();

                        InputStreamReader isr = new InputStreamReader(is);

                        int numCharsRead;

                        char[] charArray = new char[1024];

                        StringBuffer sb = new StringBuffer();

                        while ((numCharsRead = isr.read(charArray)) > 0) {

                                sb.append(charArray, 0, numCharsRead);

                        }

                        result = sb.toString();

                } catch (MalformedURLException e) {

                        e.printStackTrace();

                } catch (IOException e) {

                        e.printStackTrace();

                } finally {

                        if (httpsCon != null) {

                                httpsCon.disconnect();

                        }

                }

                return result;

        }

}

Integration with Oracle Identity Management solutions:

Oracle Privileged Account Manager can be integrated with Oracle Identity Governance, Oracle Access Management and Oracle Directory Services – the three building tiers of Oracle Identity Management Suite. OPAM provides the ability to manually request access to accounts and to get approvals for requests in Oracle Identity Manager. OPAM can be protected by enabling Single Sign On using a Webgate agent in Oracle Access Manager.

Backend:

Following is a list of tables from DEV_OPAM schema used by the Oracle Privileged Account Manager:

TARGET, ACCOUNT, GRANTS, USGPOL, PWDPOL, FAILURE, ACTSESSION, FLEXFIELD, FLEXOBJ, FLEXSECFIELD

The Metadata information and passwords managed by OPAM are encrypted and persisted in the Oracle Database. It is recommended to leverage Oracle Database Vault and Transparent Data Encryption (TDE) for additional security.

Conclusion:

Oracle Privileged Account Manager is a complete product which has a comprehensive set of features that are required to manage the password lifecycle of privileged accounts – an  activity for which there was no solution available earlier. OPAM delivers more value when used in conjunction with other Oracle Identity Management Products.

References:

http://www.oracle.com/technetwork/middleware/id-mgmt/overview/opam-wp-11gr2-1697093.pdf

http://www.oracle.com/technetwork/middleware/id-mgmt/overview/opam-ds-11gr2-1697091.pdf

http://docs.oracle.com/cd/E27559_01/admin.1112/e27152/toc.htm

OID Policystore Migration

OID Policystore Migration

                 Policystore is basically a node in the hierarchical structure of Oracle Internet Directory where all the application policies are stored. There will be cases where you will want to replicate the policystore structure to some other OID instance in development or in production mode. This is useful in cases where you want to maintain the same application policies across multiple environments. Of course you can use the same OID across different environments but it will be very difficult for troubleshooting
                 OID provides few set of commands using which a policystore can be exported to an LDIF file and then that LDIF file can be imported on another OID.
                 This blog explains the use of ldifwrite and bulkload commands which are used to export the policystore or to be specific any node to an LDIF file and import the LDIF file respectively.
                 Following environment variables must be set before proceeding:

1. WLS_HOME=<path_where_middleware_is_installed>
2. ORACLE_HOME=$WLS_HOME/Oracle_IDM1
3. ORACLE_INSTANCE=$ORACLE_HOME/asinst_1

                 Following directories must be added to the PATH variable:

1. ORACLE_HOME/bin
2. ORACLE_HOME/ldap/bin
3. ORACLE_INSTANCE/bin

                OID instance must be shut down before performing bulkload commands to avoid any inconsistencies in the loading.
                    opmnctl stopall

                Follow the below steps to replicate a node in one OID to another :

• Use ldifwrite to export a node to an ldif file :

        ldifwrite connect="connect_string" basedn="source_dn" file="location.ldif"
     e.g. If you want to export 'cn=mynode,cn=jpsContext,cn=jpsroot' (basedn)  which resides in ODS schema of OIDDB_SOURCE (connect_string as specified in ORACLE_INSTANCE/config/tnsnames.ora) to a file source.ldif which is at location (/u01/export/source.ldif), use the following command :
        ldifwrite connect="OIDDB_SOURCE" basedn="cn=mynode,cn=jpsContext,cn=jpsroot" file="/u01/export/source.ldif"

• Use bulkload to import the ldif file and generate the intermediate SQL*Loader files :

      bulkload connect="connect_string" check="true" generate="true" recover="true" file="location.ldif"
     e.g. Intermediate SQL*Loader files which are to be executed for ODS schema in OIDDB_TARGET (connect_string) can be generated from /u01/export/source.ldif (file) with the following command :
          bulkload connect="OIDDB_TARGET" check="true" generate"true" recover="true" file="/u01/export/source.ldif"

              check flag parses and verifies the input LDIF file to find any corrupt data
              generate flag generates the intermediate files in SQL*Loader format
              restore flag restores the schema in case any problem arises during bulkload operation

• Use bulkload to load the intermediate SQL*Loader files in the target OID schema :

       bulkload connect="connect_string" load="true"
      e.g. Intermediate files generated by 2 option can be loaded in the schema OIDDB_TARGET by the following command :
           bulkload connect="OIDDB_TARGET" load="true"

   After the completion of bulkload execution, start the OID server instance:
                 opmnctl startall

  The logs file generated by the bulkload tool are at location :
        ORACLE_INSTANCE/diagnostics/logs/OID/tools

1. bulkload.log : output log
2. duplicateDN.log : list of duplicate DNs found during loading
3. *.ctl and *.dat : intermediate files

        ORACLE_INSTANCE/OID/load

1. badentry.ldif : list of bad LDIF entries
2. dynGrp.ldif : list of dynamic group entries that can be added using ldapadd command
3. bsl_*.log : intermediate log files generated by SQL*Loader

      If there are any errors during indexing phase of loading, following command can re-create the indices :
           bulkload connect="OIDDB_TARGET" index="true"
      Indices can be verified by using the command :
              bulkload connect="OIDDB_TARGET" check="true" index="true"

     In this way you can migrate the application policystore or any node for that matter from one OID instance to another. The detailed explanation of all the attributes used in the above commands can be found at the location http://docs.oracle.com/cd/E25054_01/oid.1111/e10029/bulktools.htm