Uploaded image for project: 'CloverDX'
  1. CloverDX
  2. CLO-12691

Improved performance of graph log password obfuscation

    XMLWordPrintable

    Details

    • Type: Improvement
    • Status: Closed
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: rel-4-8-1
    • Component/s: None
    • Security Level: Users (General product issues)
    • Labels:
    • Story Points:
      1
    • QA Testing:
      UNDECIDED
    • Sprint:
      Green Sprint 57

      Description

      Messages written to graph log are checked before writing to the graph log file. If any password is detected, it's masked by some stars: ******

      This is done by a pattern that is very slow for larger inputs.

      I've run into this problem when using jms event listerer starting a graph. My JMS messages can be large (60KB). Content of messages is passed to graph in a graph parameter. The parameters are logged to graph log at graph start and that causes the slowdown.

      It takes 2 minutes (!!!) before my graph is started after the jms listener receives a message.

        Attachments

          Issue Links

            Activity

              People

              • Assignee:
                adamekl Lukas Adamek
                Reporter:
                salamonp Pavel Salamon
              • Votes:
                0 Vote for this issue
                Watchers:
                4 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: