[
https://issues.apache.org/jira/browse/KAFKA-2680?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14973437#comment-14973437
]
ASF GitHub Bot commented on KAFKA-2680:
---------------------------------------
GitHub user rajinisivaram opened a pull request:
https://github.com/apache/kafka/pull/357
KAFKA-2680: Use IBM ConfigFile class to load jaas config if IBM JDK
Use IBM ConfigFile class with IBM JDK since JavaLoginConfig provided by SUN
provider is not included with IBM JDK.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/rajinisivaram/kafka KAFKA-2680
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/kafka/pull/357.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #357
----
commit 3ec1ff178c5a27635e9b185c66e69f0563aa4e16
Author: Rajini Sivaram <rajinisiva...@googlemail.com>
Date: 2015-10-25T20:53:34Z
KAFKA-2680: Use IBM ConfigFile class to load jaas config if IBM JDK
----
> Zookeeper SASL check prevents any SASL code being run with IBM JDK
> ------------------------------------------------------------------
>
> Key: KAFKA-2680
> URL: https://issues.apache.org/jira/browse/KAFKA-2680
> Project: Kafka
> Issue Type: Bug
> Reporter: Rajini Sivaram
> Assignee: Rajini Sivaram
> Priority: Blocker
> Fix For: 0.9.0.0
>
>
> Vendor-specific code in JaasUtils prevents Kafka running with IBM JDK if a
> Jaas configuration file is provided.
> {quote}
> java.security.NoSuchAlgorithmException: JavaLoginConfig Configuration
> not available
> at sun.security.jca.GetInstance.getInstance(GetInstance.java:210)
> at
> javax.security.auth.login.Configuration.getInstance(Configuration.java:341)
> at
> org.apache.kafka.common.security.JaasUtils.isZkSecurityEnabled(JaasUtils.java:100)
> {quote}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
