000014747 - AXM Token Server log file rotation is not consistent with regular agent logs

Document created by RSA Customer Support Employee on Jun 14, 2016Last modified by RSA Customer Support Employee on Apr 21, 2017
Version 2Show Document
  • View in full screen mode

Article Content

Article Number000014747
Applies ToClearTrust Web Agent IIS V4.8 Agent
Token Server ctagent_tokengen.exe
IssueAXM Token Server log file rotation is not consistent with regular agent logs

The Token server uses the default log file rotation naming scheme even if process safe log file rotation is used (default).

    ct_tokengen.log.2804
    ct_tokengen.log.lock

Resolution

This issue has been addressed with Hotifix 4.8.0.10 for the 4.8 Agent for IIS 6.0.  This hotfix includes a setting that allows the Access Manager Token server (ctagent_tokengen.exe) to use a file rotation naming convention that is consistent with the regular agent logs.  In order to keep backwards compatibility for some customers who may already have standardized on the existing log file format the new naming convention is enabled by setting a configuration file entry in the webagent.conf file.

When set the new parameter ?cleartrust.agent.iis.token_server_log_consistency=True? causes the token server to use the exact same format as the agent logs.

For example with log_flags=16 and process safe log file rotation the log file will include the name of the log, the PID and the timestamp followed by .log

     ct_tokengen.20081020200357.log
     ct_tokengen.log.lock

Without the log_fags=16 bit set and process safe log file rotation the log file will include the name of the log and the timestamp followed by .log

     ct_tokengen.2821.20081020200357.log
     ct_tokengen.log.lock

Legacy Article IDa42667

Attachments

    Outcomes