Github user EronWright commented on the issue:
https://github.com/apache/flink/pull/3057
@StephanEwen updated based on feedback, thanks again.
---
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
Github user EronWright commented on the issue:
https://github.com/apache/flink/pull/3057
Thanks for the review, I'll address these comments ASAP.
---
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
Github user StephanEwen commented on the issue:
https://github.com/apache/flink/pull/3057
@EronWright Thanks for explaining. It figured it out concurrently by
looking at the updated documentation you wrote ;-) The docs are good, helped a
lot!
---
If your project is set up for it,
Github user EronWright commented on the issue:
https://github.com/apache/flink/pull/3057
@StephanEwen yes, this PR does the following:
1. isolate the configuration of kerberos credentials from how those
credentials are used
2. modularize the security code to reflect the
Github user StephanEwen commented on the issue:
https://github.com/apache/flink/pull/3057
@EronWright thanks a lot for this fix, I am looking though it now.
From the description in the JIRAs, I take that this adds the logic that
reads custom JAAS security configurations and
