[
https://issues.apache.org/jira/browse/KAFKA-20555?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18079026#comment-18079026
]
Mickael Maison commented on KAFKA-20555:
----------------------------------------
If you do that, then I'd need to pick both of these in 4.3.0 too. Also we have
3 binding votes on 4.2.1 RC3 already. None of these issues seem to be blockers
so I wonder if it's worth the churn.
> JaasBasicAuthFilter should use jakarta.annotation
> -------------------------------------------------
>
> Key: KAFKA-20555
> URL: https://issues.apache.org/jira/browse/KAFKA-20555
> Project: Kafka
> Issue Type: Bug
> Components: connect
> Affects Versions: 4.0.0, 4.0.1, 4.1.0, 4.2.0, 4.3.0, 4.0.2, 4.1.1, 4.1.2,
> 4.2.1
> Reporter: Mickael Maison
> Assignee: Mickael Maison
> Priority: Major
>
> In Kafka 4.0, we bumped Jetty to 12 and switched from javax web services to
> jakarta web services, javax.ws.rs to jakarta.ws.rs.
> However, we missed the javax.annotation.Priority usage in
> JaasBasicAuthFilter. Jetty 12 ignores javax.annotation.Priority and instead
> uses jakarta.annotation.Priority to order filters in its processing chains.
> The impact is that JaasBasicAuthFilter currently does not have a priority
> which can lead to undefined filter execution order when other Connect REST
> Extension plugins are used.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
