Also, I've opened a PR with the proposed reflective shim, for anyone that
is interested: https://github.com/apache/kafka/pull/16522
Thanks,
Greg
On Fri, Jul 5, 2024 at 3:17 PM Greg Harris wrote:
> Hi all,
>
> I've added Ismael's kip-less idea as a rejected alternative, with
> appropriate justif
Hi all,
I've added Ismael's kip-less idea as a rejected alternative, with
appropriate justification.
I'm happy to discuss this alternative, as it appears to be the best
alternative, and will be what happens if the KIP vote does not succeed.
Thanks,
Greg
On Wed, Jul 3, 2024 at 10:34 AM Greg Harri
Hi Ismael,
Thanks for the question.
> Can we not
> use the SecurityManager when it's available and fallback when it's not?
This is the strategy the KIP is proposing in the interim before we drop
support for the SecurityManager. The KIP should be stating this idea, just
more verbosely.
> I'm not
Hi Greg,
Thanks for the KIP. I'm not totally clear on why we need a KIP. Can we not
use the SecurityManager when it's available and fallback when it's not? If
so, then it would mean that whether SecurityManager is used or not depends
on the JDK and its configuration.
Ismael
On Mon, Nov 20, 2023
Hi Frédérik,
Thanks for your response! This KIP is intended to be implemented
immediately after voting, so it will appear in Kafka 3.10 or 4.0 at the
earliest.
I'm currently working on a PR and in my opinion there is very little risk
of the change slipping from a release during the implementation
Hi all,
When this KIP is intended to be implemented? As KIP-1013 is deprecating
Java 11 in AK 3.7 and removes its support in AK 4.0, maybe the KIP needs an
update.
Regards,
On Mon, Jul 1, 2024 at 10:39 PM Greg Harris
wrote:
> Hi Mickael,
>
> Thanks for the pointer to that JDK ticket, I did not
Hi Mickael,
Thanks for the pointer to that JDK ticket, I did not realize that the
legacy APIs were going to be degraded instead of removed.
I have updated the KIP to accommodate for this change in the JDK
implementation. In addition to detecting the removal of the method/classes,
it will also fal
Hi,
It looks like some of the SecurityManager APIs are starting to be
removed in JDK 23, see
- https://bugs.openjdk.org/browse/JDK-8296244
- https://github.com/quarkusio/quarkus/issues/39634
JDK 23 is currently planned for September 2024.
Considering the timelines and that we only drop support fo
Hey Ashwin,
Thanks for your question!
I believe we have only removed support for two Java versions:
7:
https://cwiki.apache.org/confluence/display/KAFKA/KIP-118%3A+Drop+Support+for+Java+7
in 2.0
8: https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=181308223
in 4.0
In both cases,
Hi Greg,
Thanks for writing this KIP.
I agree with you that handling this now will help us react to the
deprecation of SecurityManager, whenever it happens.
I had a question regarding how we deprecate JDKs supported by Apache Kafka.
When we drop support for JDK 17, will we set the “-target” optio
Hi all,
I'd like to invite you all to discuss removing SecurityManager support
from Kafka. This affects the client and server SASL mechanism, Tiered
Storage, and Connect classloading.
Find the KIP here:
https://cwiki.apache.org/confluence/display/KAFKA/KIP-1006%3A+Remove+SecurityManager+Support
11 matches
Mail list logo
