To confirm this problem check that an entry exists

This preview shows page 165 - 167 out of 349 pages.

To confirm this problem, check that an entry exists for the personal certificate that is sent to the server. Depending on the user registry mechanism, look at the native operating system user ID or Lightweight Directory Access Protocol (LDAP) server entries. To correct this problem, add the user ID to the user registry entry (for example, operating system, LDAP directory, or other custom registry) for the personal certificate identity. Chapter 13. Troubleshooting security 155
"Catalog" tablet is blank (no item displayed) in GUI application client This error message occurs when you install an ActiveX client sample application that uses the PlantsByWebSphere Active X to EJB Bridge. The cause is that the server certificate is not in the client trustore that is specified in the client.ssl.props file. Although the "com.ibm.ssl.enableSignerExchangePrompt" signer property might be set to true , the auto-exchange prompt only supports a command-line prompt. If the sample application relies on a graphical user interface and does not provide access to a command prompt, for example using standard in and standard out, the auto-exchange prompt does not function. Note: The applet client under the Client Technology Samples does not have access to the command prompt and it cannot see the auto-exchange prompt. Thus, the applet client cannot rely on the auto-exchange prompt feature. To correct this problem, retrieve the certificate manually using the retrieveSigners utility. Modifying SSL Configurations after migration using -scriptCompatibility true After migrating using scriptCompatibility true, all attributes of the SSL configurations cannot be edited through the administrative console. In particular, the hardware cryptography settings cannot be displayed or edited. By using the scriptCompatibility true flag, the SSL configurations are not migrated to the new format for support in the Version 6.1 and later releases. New capabilities were added that are not supported when the configurations are not migrated to the latest format. If you are migrating from a release prior to Version 6.1, you can use the convertSSLConfig task to convert your SSL configuration information to the centralized SSL configuration format. Stand-Alone configuration fails when digital certificates are defined with the NOTRUST option If your digital certificates are defined with the NOTRUST option, it is possible that you might receive the following error message: Trace: 2008/06/18 16:57:57.798 01 t=8C50B8 c=UNK key=S2 (0000000A) Description: Log Boss/390 Error from filename: ./bbgcfcom.cpp at line: 376 error message: BBOO0042E Function AsynchIOaccept failed with RV=-1, RC=124, RSN=050B0146, ?EDC5124I Too many open files. (errno2=0x0594003D)?? If this error appears, enter ’D OMVS,P . If you have a NOTRUST issue a large number appears under 'OPNSOCK'.

  • Left Quote Icon

    Student Picture

  • Left Quote Icon

    Student Picture

  • Left Quote Icon

    Student Picture