IBM Data and AI

Welcome to the IBM Data and AI Ideas Portal for Clients!

We welcome and appreciate your feedback on IBM Data and AI Products to help make them even better than they are today!
Before you submit an idea, please perform a search first as a similar idea may have already been reported in the portal. If a related idea is not yet listed, please create a new idea and include with it a description which includes expected behavior as well as why having this feature would improve the service and how it would address your use case.
IBM Employees:
  • Our team welcomes any feedback and suggestions you have for improving our offerings / products! This forum allows us to connect your offering / product improvement ideas with IBM product and engineering teams.

  • If you have not registered on this portal please click on the following link and register. To complete registration you will need to open the email you will receive from Aha to confirm your identity.

Additional Information:
  • The shorter URL for this site is:

  • To view our roadmaps:

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

  • Please do not use the Ideas Portal for reporting bugs - we ask that you report bugs or issues with the product by contacting IBM support.

Enhance DS Git integration for proper segregation between DTAP environments (TS003975527)

Currently, while using the Git Integration from Datastage Flow Designer, it is easy for any user to connect to any GitLab repository it had access and upload jobs inside it.

The issue comes when on a Production environment, for example, you can load a job from any GitLab repository without proper surveillance. This can lead to major security issues, since you cannot manage who can upload jobs onto any environment.

  • Avatar32.5fb70cce7410889e661286fd7f1897de Guest
  • Sep 2 2020
  • Future consideration
Who would benefit from this IDEA? Any Datastage Flow Designer user that wants to make use of the Git integration
How should it work?

There are no current workarounds for this issue.

Proposed solution: Disable the capability to pull assets from GIT in TST, ACC & PRD. Define access controls per user/user group for this functionality:

  • Ideally, for each GIT operation (push/pull assets);

  • MVP: enable/disable Git integration as a whole in Test/Acc/Prd.

The benefits of this idea is that the security concern will disappear and this solution can be used globally by ING, since it is a very good implementation and can help a lot of people to make their work much easier.

Idea Priority High
Priority Justification In order to allow the usage of GIT integration in a controlled & secure way, currently it's banned in our company because of the security leaks it exposes
Customer Name ING
  • Attach files

NOTICE TO EU RESIDENTS: per EU Data Protection Policy, if you wish to remove your personal information from the IBM ideas portal, please login to the ideas portal using your previously registered information then change your email to "anonymous@euprivacy.out" and first name to "anonymous" and last name to "anonymous". This will ensure that IBM will not send any emails to you about all idea submissions