gharris1727 commented on PR #19221: URL: https://github.com/apache/kafka/pull/19221#issuecomment-2770951005
@jvissers This change applies to more than just the authenticators, it also applies to Connect and the Tiered Storage feature. If you addressed this only for authenticators, those features would still have compatibility issues with modern Java. I'm not very familiar with Authenticators, but from a quick code read it's not obvious to me how you would substitute the implementation yourself. I also don't see the Authorizer (or any classes in the network module) declared as public API: https://kafka.apache.org/39/javadoc/index.html so if you did substitute an implementation, it would be depending on internal APIs. And SecurityManagerCompatibility is itself an internal API, please don't depend on it either 😄. All that is to say: IMHO your best alternatives if this doesn't get merged are (in decreasing preference): * Use 4.x+ * Apply this patch directly as-is and distribute your own artifacts * Write new code using the Java 18+ APIs and ignore Java 17 * Copy/modify this code for additional custom changes If this backport is important to you and/or those alternatives are unreasonable, please comment on the discussion thread to show your support: https://lists.apache.org/thread/6k942pphowd28dh9gn6xbnngk6nxs3n0 -- 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. To unsubscribe, e-mail: jira-unsubscr...@kafka.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org