GitHub user kunickiaj opened a pull request:
https://github.com/apache/kafka/pull/862
KAFKA-3199: LoginManager should allow using an existing Subject
One possible solution which doesn't require a new configuration parameter:
But it assumes that if there is already a Subject you want to use its
existing credentials, and not login from another keytab specified by
kafka_client_jaas.conf.
Because this makes the jaas.conf no longer required, a missing KafkaClient
context is no longer an error, but merely a warning.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/kunickiaj/kafka KAFKA-3199
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/kafka/pull/862.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 #862
----
commit 83fcc6c6150e9b22d82573b9935ee43a0692ffa4
Author: Adam Kunicki <a...@streamsets.com>
Date: 2016-02-04T02:35:11Z
KAFKA-3199: LoginManager should allow using an existing Subject
----
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---
