Skip to content

Kafka Connect doest not inherent user permissions. #1018

@Protocol-X

Description

@Protocol-X

Issue submitter TODO list

  • I've looked up my issue in FAQ
  • I've searched for an already existing issues here
  • I've tried running main-labeled docker image and the issue still persists there
  • I'm running a supported version of the application which is listed here

Describe the bug (actual behavior)

Kafka connect provides no support to.use keytab in this tool, only basic auth. Kafka connect is supposed to be inheriting permissions from mafka. The issue is that kafka connect has its own permissions for editing connectors, but since the tool only provides a basic authentication option, it prevents proper security when using kerberos and keytabs. Kerberos does not allow for basic auth, basically forcing an unsecured connection and allowing any user to view and edit any connectors.

Expected behavior

No response

Your installation details

All versions, issu carried over from kafkaui

Steps to reproduce

The easiest way.is to.use dynamic mode, click on configuration, go to kafka connect and add a kafka connect. Select authorization, and only basic exists. If you add no authorization, it bypasses all security for a kafka connect environment and let's any user make any edits.

Screenshots

No response

Logs

No response

Additional context

No response

Metadata

Metadata

Assignees

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions