Enabling and configuring WAS security

Follow these steps to configure WebSphere Application Server security. For versions prior to WebSphere Application Server V6, refer to the section following these tasks.
  1. Click the Server tab to open the Server view.
  2. Right-click the server name (after it has been started) and select Run Administrative console.
  3. Expand Security and click Global security to open the Configuration page.
  4. Click LDAP under User registries on the right side of the page.
  5. Enter the following values for LDAP security:
    • Server User ID - enter a user ID registered for LDAP that WAS will use to access the LDAP server
    • Server User Password - enter the password
    • Type - select SecureWay
    • Host - enter the host name. You should use the full domain name.
    • Port - use the default port of 389
    • Base Distinguished Name (DN) - enter the base distinguished name of the directory service. (For example, dc=mysystem, dc=mycompany, dc=com.) This indicates the starting point where LDAP searches the directory service.

  6. Click Ok.
  7. Enter the following values for the general properties on the Global security page:
    • Check Enable global security.
    • Uncheck Enforce Java 2 security.
    • Select Lightweight Directory Access Protocol (LDAP) user registry from the Active user registry list.

  8. Click Apply.
  9. Save the changes and close the WAS Administrative Console.
  10. Restart the server.
Related concepts
Deployment descriptor

Enabling and configuring WAS security for V5.x

Setting up WebSphere Application Server security is the same for the production and test environments. When using the test environment, however, the Administrative Console must be enabled.
  1. In the Server Configuration view, double-click the server configuration.
  2. Click the Configuration tab and check Enable administration console.
  3. Save the configuration and restart the server.
  4. In a browser window, enter http://localhost:9090/admin to open the WAS Administrative Console.
  5. Expand Security > User Registries and click LDAP to open the LDAP Security Configuration page to update the security settings for LDAP. This example uses LDAP, which is required for implementing single signon. If you select the OS/400 registry, authentication is performed using user profiles on your iSeries system.
  6. Enter the following values for LDAP security:
    • Server User ID - enter a user ID registered for LDAP that WAS will use to access the LDAP server
    • Server User Password - enter the password
    • Type - select SecureWay
    • Host - enter the host name. This is the host name that WebSphere Application Server will use when connecting to LDAP. You should use the full domain name.
    • Port - use the default port of 389
    • Base Distinguished Name (DN) - enter the base distinguished name of the directory service. (For example, dc=myhostname, dc=mycompany, dc=com.) This indicates the starting point when LDAP searches the directory service.
    • Check Ignore Case.

  7. Click OK to apply the updates. The Global Security page is displayed.
  8. Check Enabled and uncheck Enforce Java 2 Security.
  9. Specify LDAP for the Active User Registry and click OK.

  10. Save the changes and close the WAS Administrative Console.
  11. Restart the server.