IBM G210-1784-00 manual Chapter Configuring WebSphere Application Server Security

Chapter 13

Configuring WebSphere Application Server Security

The Learning Management System assumes that the WebSphere Application Server (WAS) is configured to use LDAP authentication. The WAS Administrative Console is used to configure LDAP as the active user registry and to specify the LDAP settings as part of setting up WAS Security. Before you attempt to do this, your LDAP server must be installed, running, and populated with the node within the directory tree that is the starting point for all directory searches—an identity under this node that is used by the WAS server for security purposes, and an identity used to bind to the directory.

For example, in the set-up description below, we’ll assume you’ve created an LDAP directory using the IBM Directory Server V4.1 called “ldapserver.ibm.com” that runs on default port 389 and contains a root node called “o=ibm”. In addition, the root node contains a security identity with following characteristics:

Distinguished Name: cn=ldapadmin,o=ibm

Uid:ldapadmin

Password:password

Finally, the bind identity (setup during installation of the LDAP directory) has the following characteristics:

Distinguished Name: cn=root

Password:password

Security must be configured and enabled after WAS is installed but before the Learning Management System application is deployed. This is done from the WAS Administrative Console; accessed by launching an Internet browser and navigating to http://was_server:9090/admin (substitute the name of your server for was_server).

Chapter 13: Configuring WebSphere Application Server Security 71