IBM Tivoli Federated Identity Manager, Version 6.2.2

C client cannot communicate with the Common Audit Service server

This topic describes the problem and the workaround to use if the C client is not correctly configured to communicate with the Common Audit Service audit server.

Problem

The C client cannot communicate with the Common Audit Service audit server when incorrectly configured.

Workaround

Correct mistakes in the [cars-client] stanza in the pdaudit configuration file, then restart the application. Correcting the configuration to enable auditing includes the following settings:
  • Set the doAudit property to the value yes.
  • Set the serverURL property to the correct value. To verify that the value is correct, specify the same value in the URL field of your browser to ensure that it resolves. For example, a URL value for a non-SSL server is similar to:

    http://hostname:WC_defaulthost_port_number/CommonAuditService/services/ Emitter

    A URL value for an SSL-enabled server is similar to:

    https://hostname:WC_defaulthost_secure_port_number/CommonAuditService/ services/Emitter

    A correct URL value will result in the Web browser displaying a page with contents that are similar to:
    {urn:ibm:cars:10}Emitter
    
    Hi there, this is a Web service!
  • Set the diskCachePath property to a valid value if the useDiskPath property is set to always or to auto; auto is the default value. Both values enable caching to a cache file.

    Note that a valid value for diskCachePath is a file path that already exists and includes a valid cache file name.



Feedback