-
Notifications
You must be signed in to change notification settings - Fork 433
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
IBM Semeru Runtime Certified Edition for z/OS, Kerberos and mssql-jdbc don't work together #2576
Comments
Hi @trzpiot We are looking into addressing this issue. As a temporary workaround, you can setup a JAAS config and set a correct login module,
|
muskan124947
added a commit
that referenced
this issue
Feb 11, 2025
…c don't work together #2576 (#2581) * IBM Semeru Runtime Certified Edition for z/OS, Kerberos and mssql-jdbc don't work together #2576 * Added test case * Comment * Updated test * Updated the configuration name JAAS * Testing purpose * removed local changes * Added error string and useIbmModule boolean flag * Update isIBM() * Updated the logic
fyi: Change introduced #2608 |
# for free
to join this conversation on GitHub.
Already have an account?
# to comment
Driver version
12.4.2.jre11
Client Operating System
z/OS
JAVA/JVM version
IBM Semeru Runtime Certified Edition for z/OS 17.0.7.0 (https://www.ibm.com/docs/en/semeru-runtime-ce-z/17)
Problem description
The following exception is thrown:
Same problem as with #2139.
The check in #2209 on
java.vm.name
causes still false-positives, because the IBM Semeru Runtime Certified Edition for z/OS still usesIBM J9 VM [...]
asjava.vm.name
. It then accessescom.ibm.security.auth.module.Krb5LoginModule
instead ofcom.sun.security.auth.module.Krb5LoginModule
. Only the latter is available on the Semeru runtime.The text was updated successfully, but these errors were encountered: