Hi Justin,
The RDi Kerberos check queried the 'JVM name' to determine if we should invoke the IBM kinit in the JVM or the Microsoft kinit command on the client.
The IBM SEMERU JAVA 11 no longer includes the kinit command. The supplier renamed the 'JVM name' in our 9800 version of java, and that forced us to use the Microsoft kinit command instead.
We never received any Support cases.
In 9801 version of Java, the supplier renamed the 'JVM name' back, which is why many users could no longer use Kerberos in 9801, so we opened an APAR.
We asked people using Kerberos to remain at 9800, or switch to use standard logins for 9801.
The APAR fix shipped in 9802 removed the JVM name check. We ONLY use the Microsoft kinit command now.
If your IT department worked around this issue for 9801, that could be why it no longer works in 9802.
HTH
Steve Ferrell
-----Original Message-----
From: WDSCI-L <wdsci-l-bounces@xxxxxxxxxxxxxxxxxx> On Behalf Of Justin Taylor
Sent: Tuesday, July 9, 2024 8:08 AM
To: wdsc <wdsci-l@xxxxxxxxxxxxxxxxxx>
Subject: [WDSCI-L] RDi 9.8 & Kerberos
External: Pause and review the sender's email address, any URLs before clicking links, opening attachments, or following requests. When in doubt, contact the Service Desk.
Is anyone using Kerberos with RDi 9.8.0.2?
For me, Kerberos worked in RDi up through base 9.8. With the 9.8.0.1 fix pack, Kerberos still worked except for SEPs. Starting in 9.8.0.2, Kerberos no longer works at all.
IBM support is working on my issue. I'm just curious how widespread this issue is.
Thanks
--
This is the Rational Developer for IBM i (WDSCI-L) mailing list
To post a message email: WDSCI-L@xxxxxxxxxxxxxxxxxx To subscribe, unsubscribe, or change list options,
visit:
https://lists.midrange.com/mailman/listinfo/wdsci-l
or email: WDSCI-L-request@xxxxxxxxxxxxxxxxxx
Before posting, please take a moment to review the archives at
https://archive.midrange.com/wdsci-l.
As an Amazon Associate we earn from qualifying purchases.