[
https://issues.apache.org/jira/browse/FLINK-18045?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Till Rohrmann closed FLINK-18045.
---------------------------------
Resolution: Fixed
Fixed via
master: 415b78af67e4acab9a0f23af2dc74ac093a54057
1.11.0: c8205341418d9139dc59d2fcd7b5dbae6b4c5f98
1.10.2: e71a42c7271922a4feb4f7c967213644c60841b8
> Newest version reintroduced a bug causing not working on secured MapR
> ---------------------------------------------------------------------
>
> Key: FLINK-18045
> URL: https://issues.apache.org/jira/browse/FLINK-18045
> Project: Flink
> Issue Type: Bug
> Components: Deployment / YARN
> Affects Versions: 1.10.1, 1.11.0
> Reporter: Bart Krasinski
> Assignee: Bart Krasinski
> Priority: Critical
> Labels: pull-request-available
> Fix For: 1.11.0, 1.10.2
>
>
> I was not able to run Flink 1.10.1 on YARN on a a secured MapR cluster, but
> the previous version (1.10.0) works fine.
> After some investigation it looks like during some refactoring, checking if
> the enabled security method is kerberos was removed, effectively
> reintroducing https://issues.apache.org/jira/browse/FLINK-5949
>
> Refactoring commit:
> [https://github.com/apache/flink/commit/8751e69037d8a9b1756b75eed62a368c3ef29137]
>
> My proposal would be to bring back the kerberos check:
> {code:java}
> loginUser.getAuthenticationMethod() ==
> UserGroupInformation.AuthenticationMethod.KERBEROS
> {code}
> and add an unit test for that case to prevent it from happening again
> I'm happy to prepare a PR after reaching consensus
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
