sunhaibotb opened a new pull request #9622: [FLINK-13516][test] Bump MiniKdc to 3.2.0 to fix the failure of YARNSessionFIFOSecuredITCase on Java 11 URL: https://github.com/apache/flink/pull/9622 ## What is the purpose of the change This pull request bumps `MiniKdc` to 3.2.0 to fix the failure of `YARNSessionFIFOSecuredITCase` on Java 11. The failure of `YARNSessionFIFOSecuredITCase` is due to the failure of authentication when the yarn client requests access authorization of resource manager, and subsequent retries lead to test timeout. New encryption types of `es128-cts-hmac-sha256-128` and `aes256-cts-hmac-sha384-192` (for Kerberos 5) enabled by default were added in Java 11, while the current version of `MiniKdc` used by Flink does not support these encryption types and does not work well when these encryption types are enabled, which results in the authentication failure. ## Brief change log - Bumps MiniKdc to 3.2.0 ## Verifying this change This change is already covered by existing tests, such as `YARNSessionFIFOSecuredITCase`. ## Does this pull request potentially affect one of the following parts: - Dependencies (does it add or upgrade a dependency): (**yes** / no) - The public API, i.e., is any changed class annotated with `@Public(Evolving)`: (yes / **no**) - The serializers: (yes / **no** / don't know) - The runtime per-record code paths (performance sensitive): (yes / **no** / don't know) - Anything that affects deployment or recovery: JobManager (and its components), Checkpointing, Yarn/Mesos, ZooKeeper: (yes / **no** / don't know) - The S3 file system connector: (yes / **no** / don't know) ## Documentation - Does this pull request introduce a new feature? (yes / **no**) - If yes, how is the feature documented? (**not applicable** / docs / JavaDocs / not documented)
---------------------------------------------------------------- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: [email protected] With regards, Apache Git Services
