Skip to Main Content
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
Created by Guest
Created on Feb 3, 2017

Support Secure Impersonation for DataStage Big Integrate JDBC Hive connection

We are using the JAAS configuration file (JDBCDriverLogin.conf) to implement the Kerberos authentication mechanism. In our original beta testing with PX on Hadoop , we found that DataStage assumed that the Hive SPN and cache would be used for authentication. Since this is not the case at Aetna, we implemented the following solution.

Configured the DataStage admin ID/cache to form the JDBC connection to Hive. This worked great during our infrastructure testing when running as the DataStage admin ID, but now that we are running with multiple users, we realize that the DataStage admin will need to be added to all of the various groups the applications will want to access and is not a workable solution .

Our JAAS Configuration is as follows:
JDBC_DRIVER_01 { required

Rather than granting the DS Admin ID access to all the various application groups (which will be sizable), our Hadoop engineering team suggested using secure impersonation to allow the service to act as the logged in user to access data.

Our hadoop engineering team provided the following info. The first 2 links give context, and the last one is probably most relevant to this situation.

In the meantime, we have implemented the usage of multiple stanzas to the JAAS configuration for each user. This is a manual and potentially error prone process as users would need to be added and removed. We can implement this solution for the short term, but request secure impersonation support as the strategic solution as we prepare to implement and significantly scale up usage of Big Integrate here at Aetna.