Uploaded image for project: 'OpenAM Agents'
  1. OpenAM Agents
  2. AMAGENTS-172

WPA4 does not handle oversized log messages properly

    Details

      Description

      When agent is instructed to log large log message (agent profile data for example, with debug mode turned on) it can corrupt both log buffer and output log file:

      ::
      ::
      <value>agentRootURL=https://url1/</value><value>agentRootURL=https://url2_õ3�Âù_j�2016-08-29 13:35:58.752 -0500 DEBUG [0x7fba7ebfd700:25046][source/net_ops.c:475] send_attribute_request(): status: errorzÂù_j��2016-08-29 13:35:58.752 -0500 DEBUG [0x7fba7ebfd700:25046][source/net_ops.c:997] am_agent_login(): closing connection after failureÖÂù_j��2016-08-29 13:35:58.752 -0500 DEBUG [0x7fba7ebfd700:25046][source/net_client_ssl.c:615] net_ssl_msg_callback(): SSL negotiation finished successfully (SSLOK )

      Steps to reproduce:
      1) create agent profile with xml size of more than 16K (lots of not-enforced urls for example)
      2) enable debug logging in agent

      Observed result:
      *) agent corrupts log file

      Expected result:
      *) agent does not corrupt log file and truncate log message at 8K.

        Attachments

          Activity

            People

            • Assignee:
              chris.lee Chris Lee
              Reporter:
              mareks Mareks Malnacs
              QA Assignee:
              edwardb
            • Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: