You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@flink.apache.org by "Vijayakumar Govindasamy (Jira)" <ji...@apache.org> on 2022/11/09 17:01:00 UTC
[jira] [Commented] (FLINK-12130) Apply command line options to configuration before installing security modules
[ https://issues.apache.org/jira/browse/FLINK-12130?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17631170#comment-17631170 ]
Vijayakumar Govindasamy commented on FLINK-12130:
-------------------------------------------------
[~lingyaKK] [~aljoscha] [~victor-wong] I picked 1.15.2 and applied your fix and top of it. Validated and fix is working good. I can raise PR with latest changes. If this is okay, Can you please assign the ticket to me. Will share the PR shortly
> Apply command line options to configuration before installing security modules
> ------------------------------------------------------------------------------
>
> Key: FLINK-12130
> URL: https://issues.apache.org/jira/browse/FLINK-12130
> Project: Flink
> Issue Type: Improvement
> Components: Command Line Client
> Reporter: jiasheng55
> Priority: Not a Priority
> Labels: auto-deprioritized-major, auto-deprioritized-minor, auto-unassigned, pull-request-available
>
> Currently if the user configures Kerberos credentials through command line, it won't work.
> {code:java}
> // flink run -m yarn-cluster -yD security.kerberos.login.keytab=/path/to/keytab -yD security.kerberos.login.principal=xxx /path/to/test.jar
> {code}
> Above command would cause security failure if you do not have a ticket cache w/ kinit.
> Maybe we could call _org.apache.flink.client.cli.AbstractCustomCommandLine#applyCommandLineOptionsToConfiguration_ before _SecurityUtils.install(new SecurityConfiguration(cli.configuration));_
> Here is a demo patch: [https://github.com/jiasheng55/flink/commit/ef6880dba8a1f36849f5d1bb308405c421b29986]
--
This message was sent by Atlassian Jira
(v8.20.10#820010)