IBM WebSphere V5.0 Security - CGISecurity

1. Open the ikeyman tool that comes with WebSphere, able to handle the .jks
files, then open the server trust store file; if you are using the dummy
keystore, open the \etc\DummyServerTrustFile,jks.
2. Import the LDAPSSLServer.arm as a signer certificate; use the file from the
Domino server, you will have to copy the .arm file to your WebSphere server
machine.
3. Close the ikeyman utility.
To create a new SSL entry and configure WebSphere to use it to connect to the
LDAP server, follow the steps from “Configuring the secure LDAP (LDAPS)
connection” on page 328 using the following information.
iPlanet Directory Server
In this section, we will cover the steps required to configure WebSphere with
Netscape’s iPlanet Directory Server V5.0. In this scenario, we have installed
Access Manager using the native installation method.
Configuring WebSphere to use iPlanet Directory Server
In order to configure WebSphere’s access to iPlanet Directory Server, we must
first define a user entry for WebSphere to use for binding to the directory, as we
did for IBM Directory Server.
The only change we have made is that we are now using a directory suffix of
o=tamral,c=us instead of o=itso.
After you have created your user entry, WebSphere is ready to be configured to
use iPlanet Directory Server as its user registry.
1. Start the WebSphere Administrator’s Console. Once you have started the
console, log in and select Security -> User Registries -> LDAP. This will
display the LDAP User Registry panel.
2. Fill out the LDAP configuration page as follows:
– Server User ID: enter either the fully qualified Distinguished Name (DN) or
the WebSphere server ID user; we used the DN:
cn=wasadmin,o=tamral,c=us.
– Server User Password: enter the password for your user ID.
– Type: Netscape.
– Host: enter the fully qualified DNS name of your iPlanet Directory Server.
In our configuration, our host name is tivoli9.svo.dfw.ibm.com.
– Port: 389
472 IBM WebSphere V5.0 Security Handbook