[jira] [Commented] (KAFKA-12651) Connect should register REST extensions before REST resources

["Chris Egerton (Jira)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/KAFKA-12651?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17318793#comment-17318793 ] 

Chris Egerton commented on KAFKA-12651:
---------------------------------------

Whoops, turns out the REST resources aren't online immediately after being registered and are only brought up at a [later point|https://github.com/apache/kafka/blob/db688b1a5e5904eed5849fbab4940585e5a3d646/connect/runtime/src/main/java/org/apache/kafka/connect/runtime/rest/RestServer.java#L306]. By this point all REST extensions have been registered so there's no need for any changes here.

> Connect should register REST extensions before REST resources
> -------------------------------------------------------------
>
>                 Key: KAFKA-12651
>                 URL: https://issues.apache.org/jira/browse/KAFKA-12651
>             Project: Kafka
>          Issue Type: Bug
>          Components: KafkaConnect
>    Affects Versions: 2.0.0, 2.0.1, 2.1.0, 3.0.0, 2.2.0, 2.1.1, 2.0.2, 2.3.0, 2.1.2, 2.2.1, 2.2.2, 2.4.0, 2.3.1, 2.2.3, 2.5.0, 2.3.2, 2.4.1, 2.6.0, 2.4.2, 2.5.1, 2.7.0, 2.5.2, 2.6.1, 2.8.0, 2.7.1, 2.6.2, 3.1.0, 2.6.3, 2.9, 2.7.2, 2.8.1
>            Reporter: Chris Egerton
>            Assignee: Chris Egerton
>            Priority: Major
>
> Connect currently registers custom REST extensions after REST resources. This can be problematic in security-conscious environments where REST extensions are used to lock down access to the Connect REST API, as it creates a window of opportunity for unauthenticated access to the REST API between the time the worker's REST resources are brought up and when its REST extensions are registered.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)