Skip to Main Content
Cloud Platform


This is an IBM Automation portal for Cloud Platform products. To view all of your ideas submitted to IBM, create and manage groups of Ideas, or create an idea explicitly set to be either visible by all (public) or visible only to you and IBM (private), use the IBM Unified Ideas Portal (https://ideas.ibm.com).


Shape the future of IBM!

We invite you to shape the future of IBM, including product roadmaps, by submitting ideas that matter to you the most. Here's how it works:

Search existing ideas

Start by searching and reviewing ideas and requests to enhance a product or service. Take a look at ideas others have posted, and add a comment, vote, or subscribe to updates on them if they matter to you. If you can't find what you are looking for,

Post your ideas
  1. Post an idea.

  2. Get feedback from the IBM team and other customers to refine your idea.

  3. Follow the idea through the IBM Ideas process.


Specific links you will want to bookmark for future use

Welcome to the IBM Ideas Portal (https://www.ibm.com/ideas) - Use this site to find out additional information and details about the IBM Ideas process and statuses.

IBM Unified Ideas Portal (https://ideas.ibm.com) - Use this site to view all of your ideas, create new ideas for any IBM product, or search for ideas across all of IBM.

ideasibm@us.ibm.com - Use this email to suggest enhancements to the Ideas process or request help from IBM for submitting your Ideas.


Status Delivered
Workspace UrbanCode
Categories Deploy
Created by Guest
Created on Jan 26, 2017

suppport X-Forwarding-For and log true client ip as well as source ip address to audit logs

We need the true client IP address as well as source client ip logged in audit logs such as DS_AUDIT_ENTRY.
This could be achieved by UCD application checking for existence of "X-Forwarded-For" HTTP header and this logging value in addition to the TCP client IP address (which is not the true client ip address in a load balanced HA solution configuration)

Currently a UrbanCode Deploy HA solution configured with configured with load balancer only log the TCP source IP address (which is the IOP address of the load balancer and not true source IP address).

Ideally both IP addresses (actual and load balancer-provided) would be shown in the audit logs and via the GUI Web interface.

Idea priority Medium
RFE ID 100162
RFE URL
RFE Product UrbanCode Deploy
  • Admin
    Osman Burucu
    Reply
    |
    Apr 29, 2022

    Hello Patrick,

    Please create a support ticket and add this RFE link to it with the request for clarification. I will then forward the case number to my colleague from dev to have a look at it.

  • Guest
    Reply
    |
    Apr 29, 2022

    Hello @Osmam Burucu

    please be so kind to point us to the documentation as to how we can enable client IP in the audit logs. Currently we still only see loadbalancer IP in the audit logs (GUI + log file). We are running on UCD 7.2.2.1

    Thank you

  • Admin
    Osman Burucu
    Reply
    |
    Apr 29, 2022

    Implemented in 7.1.1.0

  • Guest
    Reply
    |
    Oct 2, 2020

    The feature that is described in this request is a candidate for a future release.

  • Guest
    Reply
    |
    Feb 27, 2019

    If you just want to log the incoming headers called: "X-Forwarded-For", you can do the following:



    1) Stop the UCD server



    2) Make a backup of the file:



    \opt\tomcat\conf\server.xml



    3) Find the line that states:







    4) Add this line just after it:


    prefix="localhost_access_log" suffix=".txt"

    pattern="%t %{X-Forwarded-For}i" />



    5) Restart the server



    Results:



    You will find a file called something like:



    \opt\tomcat\logs\localhost_access_log.2019-02-11.txt



    containing text like the following:



    [11/Feb/2019:13:09:21 +0100] 140.211.11.130, 192.168.0.10



    The general format of the field is:

    X-Forwarded-For: client, proxy1, proxy2

    where the value is a comma+space separated list of IP addresses, the left-most being the original client, and each successive proxy that passed the request adding the IP address where it received the request from. In this example, the request passed through proxy1, proxy2, and then proxy3 (not shown in the header). proxy3 appears as remote address of the request.

    If you are using Agent Relays, the following might be more useful:

    server.xml


    internalProxies="\d{1,3}\.\d{1,3}\.\d{1,3}\.\d{1,3}"

    remoteIpHeader="x-forwarded-for"

    proxiesHeader="x-forwarded-by"

    protocolHeader="x-forwarded-proto"/>

  • Guest
    Reply
    |
    Feb 8, 2017

    Although the theme of this request is consistent with our business strategy, it is not committed to the release that is currently under development.