Log actual remote IP addresses and exclude private IPs during backend processing

XMLWordPrintable

    • 2
    • 1

      Currently, when a user performs an action that triggers backend processing (such as viewing an attachment), the audit log records an internal IP address (e.g., 10.xxx.xxx.xxx) instead of the user's actual remote IP address.

      This is causing issues for customers who are auditing user activity.

      It would be helpful if private IP addresses from backend processing were either filtered out or replaced with the client's actual IP address.

      Example actions :

      • Moved Confluence page on site XXX
      • Viewed Confluence attachment XXX in site XXX
      • Updated page template on site XXX

              Assignee:
              Unassigned
              Reporter:
              K.Kitajima
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

                Created:
                Updated: