IBM Data and AI Ideas Portal for Customers

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:

Post your ideas

Post ideas and requests to enhance a product or service. Take a look at ideas others have posted and upvote them if they matter to you,

  1. Post an idea

  2. Upvote ideas that matter most to you

  3. Get feedback from the IBM team to refine your idea

Help IBM prioritize your ideas and requests

The IBM team may need your help to refine the ideas so they may ask for more information or feedback. The product management team will then decide if they can begin working on your idea. If they can start during the next development cycle, they will put the idea on the priority list. Each team at IBM works on a different schedule, where some ideas can be implemented right away, others may be placed on a different schedule.

Receive notification on the decision

Some ideas can be implemented at IBM, while others may not fit within the development plans for the product. In either case, the team will let you know as soon as possible. In some cases, we may be able to find alternatives for ideas which cannot be implemented in a reasonable time.

Additional Information

To view our roadmaps:

Reminder: This is not the place to submit defects or support needs, please use normal support channel for these cases

IBM Employees:

The correct URL for entering your ideas is:

Status Future consideration
Workspace Cloud Pak for Data
Created by Guest
Created on Jan 14, 2021

Log the Source Client IP Address in the system logs / audit logs

As per our security requirements, we need to see the IP Address of the machine from where the user has accessed the IBM Cloud Pak for Data web console. In the current system, we don't see any evidence for the same. I have worked with the support team and as per their recommendation, I am raising this. The reference to the support ticket is TS004726749

Needed by Date Feb 1, 2021
  • Guest
    May 5, 2021

    Any update on this.

    It has been quite some time since we had the last update on this.

    Any progress in enabling this?

  • Guest
    Apr 1, 2021

    Our clients had requesting for this as well

  • Guest
    Feb 26, 2021

    Dear Matthew,

    Thanks for the details of the conversations which you had.

    Looking forward for the procedure or SOP for getting this enabled as soon as possible.

    Appreciate your response.

    Thanks and Regards,

    Muni Kumar

  • Guest
    Feb 26, 2021

    Thank you for the input. I am continuing to discuss this requirement with our audit development team who is investigating. Status I can relay as of today is:

    • CP4D implementation today already extracts the client IP address (X-Forwarded-For header or Remote Address) and set the AUDIT-initiator-host-address request header for inclusion in all resulting Audit Records

    • However, the X-Forwarded headers are by default masked/substituted by OCP route behavior prior to actually reaching CP4D (nginx), therefore the external IP never reaches CP4D and cannot be logged

    • OpenShift 3.11 allowed OCP route configuration change to allow passthrough of this information, IBM documented how this configuration can be changed when OCP 3.11 is being used

    • Similar Openshift 4.x route configuration options have not worked successfully to allow similar passthrough.

    • Openshift 4.6 includes options for additional control over X-Forwarded headers. Our development team is actively investigating configuration options that would allow passthrough to function as requested.

  • Guest
    Jan 15, 2021

    This is most critical info where security team requested for