Skip to content
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

Closed
trzpiot opened this issue Jan 7, 2025 · 2 comments · Fixed by #2581
Closed
Assignees

Comments

@trzpiot
Copy link

trzpiot commented Jan 7, 2025

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:

javax.security.auth.login.LoginException (No LoginModule found for com.ibm.security.auth.module.Krb5LoginModule)

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 uses IBM J9 VM [...] as java.vm.name. It then accesses com.ibm.security.auth.module.Krb5LoginModule instead of com.sun.security.auth.module.Krb5LoginModule. Only the latter is available on the Semeru runtime.

@github-project-automation github-project-automation bot moved this to To be triaged in MSSQL JDBC Jan 7, 2025
@machavan machavan self-assigned this Jan 8, 2025
@machavan machavan added the Under Investigation Used for issues under investigation label Jan 8, 2025
@machavan
Copy link
Contributor

machavan commented Jan 9, 2025

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,

  • using jaasConfigurationName connection property
  • or programmatically overriding the JAAS config and use the useDefaultJaasConfig connection property

@machavan machavan moved this from To be triaged to Backlog in MSSQL JDBC Jan 9, 2025
@machavan machavan moved this from Backlog to Under Investigation in MSSQL JDBC Jan 9, 2025
muskan124947 added a commit that referenced this issue Jan 10, 2025
@machavan machavan moved this from Under Investigation to Under Peer Review in MSSQL JDBC Jan 13, 2025
@muskan124947 muskan124947 added Under Review Used for pull requests under review and removed Under Investigation Used for issues under investigation labels Jan 30, 2025
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
@github-project-automation github-project-automation bot moved this from Under Peer Review to Closed Issues in MSSQL JDBC Feb 11, 2025
@Jeffery-Wasty Jeffery-Wasty removed the Under Review Used for pull requests under review label Feb 11, 2025
@MrEasy
Copy link
Contributor

MrEasy commented Feb 17, 2025

fyi: Change introduced #2608

# for free to join this conversation on GitHub. Already have an account? # to comment
Labels
None yet
Projects
Status: Closed Issues
5 participants