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: http://ibm.biz/Data-and-AI-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: https://hybridcloudunit-internal.ideas.aha.io


Workspace Spectrum Conductor
Components Future Version
Created by Guest
Created on Jun 9, 2021

PySpark Kernel unable to read/extract when connected to external database using Kerberos Keytab

IBM JRE supplied as part of Sym 7.3.1 + Conductor 2.5 is incompatible with current use-case

Use-case: We have a client that uses Spark/Notebooks (PySpark kernel) to connect an external database via ODBC using kerberos. Whenever they try to connect to external DB using IBM supplied versions of JRE (see below) - they are encountering

"unable to find LoginModule class: com.sun.security.auth.module.Krb5LoginModule"

It is supposed to look for com.ibm.security.auth.module.Krb5LoginModule instead but that isn't the case.


[egoadmin@cbbenp13-cc017 ~]$ cd /opt/middleware/symphony/jre/
[egoadmin@cbbenp13-cc017 jre]$ ls -ltr
total 20
drwxr-xr-x. 3 egoadmin cbb 4096 May 11 12:20 8.0.6.0
drwxr-xr-x. 3 egoadmin cbb 4096 May 11 12:22 8.0.6.20


Both these versions (8.0.6.0 , 8.0.6.20) do not work for current clients use-case when we point the JAVA_HOME to the associated jre


Upon on checking with Support team on this issue, we were provided with OpenJDK (see below) - now, they are able to read data properly however encounter errors when they try to see the content. We need to understand what really happens behind show() that involves Kerberos

[egoadmin@cbbenp13-cc017 ~]$ cd /opt/middleware/symphony/jre/
[egoadmin@cbbenp13-cc017 jre]$ ls -ltr
total 20
drwxr-xr-x. 8 egoadmin cbb 4096 Jun 18 2020 jdk1.8.0_261 --- Provided by Ding from support team

df_table.show() throws an error

" Error: The service in process is not supported. Unable to find valid kerberos
principal for authentication"


This is odd to me, as the Spark read works , but when we view the dataframe it doesnt work - See below

(Below snippet works fine)

jdbcurl = "jdbc:oracle:thin:@//iaasn00095176.svr.us.jpmchase.net:6136/CPA_DEV_DP109649_180221220944_J_READWRITE"


df_table = spark.read.format("jdbc").option("url",jdbcurl) \
.option("dbtable", "(SELECT * FROM sys.dual)") \
.option("oracle.jdbc.allowedLogonVersion","8") \
.option("oracle.net.kerberos5_mutual_authentication","true") \
.option("oracle.net.authentication_services","( KERBEROS5)") \
.option("Driver","oracle.jdbc.OracleDriver") \
.option("oracle.net.kerberos5_cc_name","/cpa/fs1/deploy/keys_ea/krb5cc_309936") \
.load()

We also need your help to understand what happens behind .show()

  • Guest
    Jun 16, 2021

    What we want is either:
    A) a new IBM JDK that uses the correct IBM driver and/or class to connect as expected from the error log.
    Or
    B) A fix so that it uses the default oracle log that is already provided in the JDK, and the error does not expect the IBM implemenation.

  • Guest
    Jun 15, 2021

    Hi IBM Team,

    Has there been any update on this RFE. This is a blocker for one of our key clients.

    Please feel free to setup a debug session if you would like to