Legal | Privacy
Configuring SSL for Oracle Internet Directory and Microsoft Active Directory Integration

Configuring SSL for Oracle Internet Directory and Microsoft Active Directory Integration

This module provides instructions to configure SSL for OID and ADS integration.

Topics

This module covers the following topics:

Place the cursor on this icon to display all screenshots. You can also place the cursor on each icon to see only the screenshot associated with it.

Overview

This module provides steps that must be completed before configuring the export connector.

Prerequisites

Before starting this module, you should have:

1.

Installed Oracle Application Server 10g Instance

2.

Verified whether OID server is functional

Configuring the External Authentication Plug-in Policy

Use External Password Authentication if you want some or all of your Oracle 10g Application Server users to authenticate by using their user credentials stored in Active Directory, or if you do not want your Active Directory user passwords to be stored in OID. External Password Authentication allows you to set up OID so that when a user authenticates against OID, OID checks the users credentials against the Active Directory server rather than OID.

Another reason to set up external authentication is because Active Directory import connector cannot migrate hashed passwords from Active Directory to OID. This is because Microsoft uses a proprietary hashing algorithm called Unicode password encryption that is not supported in OID. Therefore, if you want to authenticate by using your Microsoft password, you must set up the External Password Plug-in.

1.
2.

Enter the password for the orcladmin user.

Now, enter the subscriber search base. This is the DN of the users container in OID that you want to authenticate to AD.

Leave Plug-in Request Group DN blank. Press [Enter] without a value.

The Exception Entry Property value acts as a filter and determines which users will authenticate against OID and which users will authenticate against AD. If you leave this value as null, all users in your realm will authenticate by using their credentials stored in AD.

For example, the value (&(objectclass=inetorgperson)(cn=orcladmin)) indicates to OID that every user except the user "cn=orcladmin" will authenticate by using the credentials stored in AD.

Here, do not set up the backup Active Directory failover. Select n for no.

 

Configuring a New OID SSL Server Configset

To synchronize passwords from OID to AD, it is necessary that you set up OID to communicate with the AD server over SSL. Configsets in OID allow you to configure custom startup settings for the OID server. By calling a specific configset when you start OID, you invoke whatever parameters are associated with that configset. To create a new configset with SSL parameters needed for running OID in SSL mode, perform the following steps:

1.
2.

Move your mouse over this icon to see the image

 

 

3.

Select the green box from the menu to create a new configset.

Move your mouse over this icon to see the image

 


4.

You can configure your new configset in the Configuration Set2 form. Enter the following values:

In the SASL Mechanism field, enter:

DIGEST-MD5

In the SASL Cypher Choice field, enter:

DIGEST-MD5

DES

3DES

In the Non SSL Port field, enter a port number such as 3060.

Click OK. You should now see a new configset in your list of Directory Server.

Move your mouse over this icon to see the image

 

 

5.

Select your new configset. Select the SSL Settings tab.

Move your mouse over this icon to see the image

 

 

6.

Make the following changes:
Set the SSL Authentication to SSL Server Authentication.
Set the SSL Enable field to Both SSL and Non-SSL.
Set the SSL Wallet URL to the location where your wallet exists. For now, you can set the SSL Wallet URL to the location where you will eventually create a new wallet. Enter file:/u01.
Set the SSL port number.

Move your mouse over this icon to see the image

 

 

7.

Restart the OID Server by using your new server configset.

#oidctl connect=>DB_connect> server=oidldapd instance=1 stop
#oidctl connect=<DB_connect> server=oidldapd instance=1 configset=2 start

Move your mouse over this icon to see the image

 

 

 

Creating a Wallet for SSL Connectivity Between OID and AD

You must configure a wallet that is necessary for SSL connectivity between OID and AD. This enables you to safely move sensitive data such as passwords between OID and AD.

1.

2.

If you get a message indicating that your default wallet directory does not exist and prompts you if you want to create it, select No.

Move your mouse over this icon to see the image

 

Move your mouse over this icon to see the image

 

 

3.

Enter a password for the new wallet. Remember this password because you will need it later. Click OK.

Move your mouse over this icon to see the image

 

 

4.

When prompted to create a certificate request, select Yes.

Move your mouse over this icon to see the image

 

 

5.

In the Certificate Request Form, enter the following details:

Common Name: OID to AD cert req
Organizational Unit: OID server
Organization: Oracle Corp
Locality/City: Colorado Springs
State/Province: Colorado
Select United States from the Country list.
Change the Key Size to 1024 bits.

Click OK.

Move your mouse over this icon to see the image


6.

Your request for the certificate is now complete.

Move your mouse over this icon to see the image


7.

Move the certificate request file from the server to your PC by using FTP. Copy the contents of the file.

Move your mouse over this icon to see the image

 

Move your mouse over this icon to see the image

 

 

8.

Open a new browser and navigate to the Oracle Certificate Authority user page. Click the Server / SubCA Certificates tab.

Move your mouse over this icon to see the image

 

 

9.

Click Request a Certificate.

Move your mouse over this icon to see the image

 

10.

Paste the certificate request in the PKCS#10 Request field.

Move your mouse over this icon to see the image

 

 

11.

Enter the contact information:

Name:
E-Mail ID:

Click Submit.

Move your mouse over this icon to see the image


12.

Note the request ID. Click OK.

Move your mouse over this icon to see the image

 

 

13.

Open a new browser and navigate to the Oracle Certificate Authority administration page. Click the Certificate Management tab.

Move your mouse over this icon to see the image

 

 

14.

Select your certificate and click OK.

Move your mouse over this icon to see the image

 

 

15.

Select your certificate request and click View Details.

Move your mouse over this icon to see the image

 

 

16.

Verify the certificate details and click Approve.

Move your mouse over this icon to see the image

 

 

17.

View the certificate request approval information and note the serial number of the issued certificate. Click OK.

Move your mouse over this icon to see the image

 

 

18.

Navigate back to the Oracle Certificate Authority user page. Click the Server / SubCA Certificates tab.

Move your mouse over this icon to see the image

 

 

19.

Verify whether Certificate and ID / Serial No. are selected in the Search fields. Enter your serial number in the text field and click Go.

Move your mouse over this icon to see the image

 

 

20.

Select the serial number and click View Details.

Move your mouse over this icon to see the image

 

 

21.

Select the certificate. Right-click and select Copy.

Move your mouse over this icon to see the image


22.

Save the contents of the certificate to your local machine.

Move your mouse over this icon to see the image


23.

Navigate to the Oracle Certificate Authority user page. Click the Server / SubCA Certificates tab.

Move your mouse over this icon to see the image


24.

Click Download CA Certificate.

Move your mouse over this icon to see the image


25.

Click Advanced.

Move your mouse over this icon to see the image

 

 

26.

Select the contents of the Base64-Encoded Certificate.

Move your mouse over this icon to see the image

 

 

27.

Save the contents of the certificate to your local machine.

Move your mouse over this icon to see the image

 

 

28.

Transfer the two files to your OID server.

Move your mouse over this icon to see the image

 

 

29.

Locate and open your AD root certificate file. Click the Details tab. Select Copy to File.

Move your mouse over this icon to see the image

 

 

30.

Click Next in the Certificate Export Wizard screen.

Move your mouse over this icon to see the image

 

 

31.

Select Base-64 encoded X.509 (.CER) format. Click Next.

Move your mouse over this icon to see the image

 

 

32.

Select your root certificate. Click Next.

Move your mouse over this icon to see the image

 

 

33.

Click Finish. Click OK in the Certificate Export Wizard. Click OK.

Move your mouse over this icon to see the image

 

Move your mouse over this icon to see the image

 

Move your mouse over this icon to see the image

 

 

34.

Transfer the root certificate to the OID server.

Move your mouse over this icon to see the image

 

 

 

Importing Your New Certificate and Trust Points into Your Wallet

Next, complete the wallet and test it to make sure it is working. To import the root certificate issued by the Oracle Certificate Authority, perform the following steps:

1.

Open Oracle Wallet Manager. Select Import Trusted Certificate from the Operations menu.

Move your mouse over this icon to see the image

 

 

2.

In the Import Trusted Certificate dialog box, select Select a file that contains the certificate. Click OK.

Move your mouse over this icon to see the image

 

 

3.

Navigate to the directory where your OCA root certificate file is located. Select the OCA root certificate file. Click OK. You should now see the new trusted certificate in the Trusted Certificate tree.

Move your mouse over this icon to see the image

 

Move your mouse over this icon to see the image

 

 

4.

Click Operations menu in Oracle Wallet Manager. Select Import User Certificate.

Move your mouse over this icon to see the image

 

 

5.

In the Import Certificate dialog box, select Select a file that contains the certificate. Click OK.

Move your mouse over this icon to see the image

 

 

6.

Navigate to the directory where your new user certificate is located. Select the user certificate file. Click OK.

Move your mouse over this icon to see the image

 

 

7.

After this, you should see the certificate status change from Requested to Ready.

Move your mouse over this icon to see the image

 

 

8.

The root certificate from the AD server must also be imported into the wallet. From the Operations menu, select Import Trusted Certificate. Navigate to the directory where your AD root certificate is located. Select the AD root certificate file. Click OK.

Move your mouse over this icon to see the image

 


9.

After this, you should see another new trusted certificate in the Trusted Certificate tree.

Move your mouse over this icon to see the image

 


10.

From the Wallet menu, select Auto Login. Click Save As to save the wallet to a file.

Move your mouse over this icon to see the image

 


11.

Save the wallet to a file. Save the file to the /u01 directory.

Move your mouse over this icon to see the image

 


12. Enter the following test command to verify whether you are able to bind to the AD server's SSL port from the OID server side:

ldapbind -p 636 -h 138.1.145.160 -U 2 -P wallet_password -W file:/u01

Move your mouse over this icon to see the image

 

 

 

Configuring the DIP Server for SSL

For the DIP server to also communicate over SSL, you must configure a wallet and wallet password file for the DIP server.

1.
2.

In this file, you see three default lines. They are:

regWalletFile: conf/srvWallet

certWalletFile: <Absolute Path of the Wallet Directory>

certWalletPwdF: <Absolute Path of the WalletPasswordFile>/certWalletPwd

In this file, the first line reads:

regWalletFile: conf/srvWallet

Leave this line alone and do not change it at all.

The middle line reads:

certWalletFile: <Absolute Path of the Wallet Directory>

Enter the path to your ewallet.p12 file. This is the wallet file that was created earlier.

Example, if your wallet file is located in a directory called /u01/app/oracle/product/904/ldap/odi/conf, then this line would look like this:

certWalletFile: /u01/app/oracle/product/904/ldap/odi/conf

Do not include the name of the wallet file in this line.

The last line in the file looks like this by default:

certWalletPwdF: <Absolute Path of the WalletPasswordFile>/certWalletPwd

This is the location of the encrypted wallet password file that the DIP server will use to access the wallet. This file has not been generated yet but will be generated in the next step. However, it is necessary for you to set the location of the file before it exists.

For instance, if you plan to put the encrypted wallet password file in a directory called /u01/app/oracle/product/904/ldap/odi/conf and you want to name the encrypted wallet password file certWalletPwd, then this last line will look like this:

certWalletPwdF: /u01/app/oracle/product/904/ldap/odi/conf/certWalletPwd

 

 

3. Copy the ewallet.p12 file you created on the previous page to the $ORACLE_HOME/ldap/odi/conf directory.

Example:

# cp /u01/ewallet.p12 $ORACLE_HOME/ldap/odi/conf

 

 

4. Create the certWalletPwd file.

Example:

# dipassistant wpasswd

This command will read the information in your odi.properties file for the location where it will create this file. When prompted, enter the password for the wallet you created previously.

 

 

Configuring the OID Reversible Password

To synchronize passwords from OID to AD, it is necessary to set up a reversible encrypted password for users. This password is in addition to the userpassword attribute, which already exists for all users. Whenever a user changes his password on the OID side, the password is typically stored by using a one-way hash algorithm, such as SSHA.

This form of the password is not compatible with the proprietary Unicodepassword attribute in AD. So you must have a clear text password to send to the AD server. This Unicode hashing algorithm is proprietary to Microsoft. When synchronizing with other LDAP server, such as iPlanet from Sun, this step is not necessary because this LDAP server supports the more open and commonly used hashing algorithm such as SHA, SSHA, MD5, MD4, and Crypt to name a few, which are also supported in OID.

If you enable the password policy in OID for User Password Reversible Encryption, then OID will enable you to store the password in the new attribute that will store an encrypted version of the password that can also be decrypted by the DIP server.

The attribute that stores this reversible password is called orclreversiblepassword.

1.
2.

Move your mouse over this icon to see the image

 

 

3.

On the General tabbed page, you see an option called User Password Reversible Encryption.

Change the value of this option to Enable.

Apply the change.

This new password attribute will not be populated until the user changes his password.

Move your mouse over this icon to see the image

 


Place the cursor over this icon to hide all screenshots.

Copyright © 2004 Oracle Corporation. All Rights Reserved.

 

E-mail this page
Printer View Printer View
Oracle Is The Information Company About Oracle | Oracle RSS Feeds | Careers | Contact Us | Site Maps | Legal Notices | Terms of Use | Privacy