Testing security after enabling it


Basic tests are available that show whether the fundamental security components are working properly. Use this task to validate the security configuration.

After configuring administrative security and restarting all of the servers in a secure mode, validate that security is properly enabled.

There are a few techniques that we can use to test the various security login types. For example, we can test the Web-based BasicAuth login, Web-based form login, and the Java client BasicAuth login.

Basic tests are available that show whether the fundamental security components are working properly. Complete the following steps to validate the security configuration:

 

  1. After enabling security, verify that the system comes up in secure mode.

  2. Test the Web-based BasicAuth with Snoop, by accessing the following URL: http://hostname.domain:9082/snoop.

    A login panel is displayed. If a login panel does not display, then a problem exists. If the panel appears, type in any valid user ID and password in the configured user registry.

    The Snoop servlet is only available in the domain if we included the DefaultApplication option when adding the appserver to the cell. The -includeapps option for the addNode command migrates the DefaultApplication option to the cell. Otherwise, skip this step.

  3. Test the Web-based form login by starting the admin console: http://hostname.domain:port_number/ibm/console.

    A form-based login page is displayed. If a login page does not appear, try accessing the admin console by typing https: //myhost.domain:9043/ibm/console.

    Type in the admin user ID and password that are used for configuring the user registry when configuring security.

  4. Test Java Client BasicAuth with dumpNameSpace.

    Use the APP_ROOT/bin/dumpNameSpace.bat file. A login panel appears. If a login panel does not appear, there is a problem. Type in any valid user ID and password in the configured user registry.

  5. Test all of the applications in secure mode.

  6. If all the tests pass, proceed with more rigorous testing of the secured applications. If we have any problems, review the SYSOUT and SYSPRINT logs.

    See on common problems, see Troubleshooting security configurations.

 

Results

The results of these tests, if successful, indicate that security is fully enabled and working properly.


Web component security
Administrative roles and naming service authorization

 

Related tasks


Secure enterprise bean applications

 

Related


Security: Links