Enabling trace logging of the cipher suites on the client side of secured communications

  1. Open the SecurityConfigurationLogger.xml file in LAWDIR/system.
  2. Enable logging for the following: 
    
            com.lawson.security.authen
            com.lawson.security.encryption
    1. Modify the SecurityAuthenFilter section (or add if necessary), so that its log level is 11.
    2. Add a section after the Consumers section that defines producer filters, and add a filter for the com.lawson.security.encryption, com.lawson.security.common, com.lawson.security.authen, and com.lawson.security.spi packages.

      For examples of SecurityLoggerConfiguration.xml modfications, see the section "Sample SecurityLoggerConfiguration.xml Modifications".

  3. Save and close the file.
  4. Restart the client that uses cipher suites, such as WebSphere, DSSO, or LASE (when functioning as a client, such as in LSF-Landmark communication). When you restart the client, the log file will show the supported and enabled cipher suites on the client side, provided the client is using a SecuredConnection object from sec-client.jar or lawson-httpclient.jar for the communication.