Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

IBM Semeru Runtime Certified Edition for z/OS, Kerberos and mssql-jdbc don't work together #2576

Open
trzpiot opened this issue Jan 7, 2025 · 1 comment
Assignees
Labels
Under Investigation Used for issues under investigation

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
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Under Investigation Used for issues under investigation
Projects
Status: Under Investigation
Development

No branches or pull requests

2 participants