Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Wrong RBAC for Kafka Connect #426

Open
4 tasks done
fallen-up opened this issue May 28, 2024 · 2 comments
Open
4 tasks done

Wrong RBAC for Kafka Connect #426

fallen-up opened this issue May 28, 2024 · 2 comments
Labels
area/rbac Related to Role Based Access Control feature status/triage/completed Automatic triage completed status/triage/manual Manual triage in progress type/bug Something isn't working

Comments

@fallen-up
Copy link

fallen-up commented May 28, 2024

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)

now it requires "edit" acl for pause and resume connectors, although it's valid for "restart" rights.

Expected behavior

No response

Your installation details

1.0.0

Steps to reproduce

use config

                - resource: connect
                  value: ".*"
                  actions: [ "view", "restart" ]

and try to pause connector.
you can do it, only if you have edit acl

Screenshots

No response

Logs

No response

Additional context

No response

@fallen-up fallen-up added status/triage Issues pending maintainers triage type/bug Something isn't working labels May 28, 2024
@kapybro kapybro bot added status/triage/manual Manual triage in progress area/rbac Related to Role Based Access Control feature status/triage/completed Automatic triage completed and removed status/triage Issues pending maintainers triage labels May 28, 2024
@fallen-up
Copy link
Author

it's meshed with provectus/kafka-ui#4170, but there the author asked for a new type of access. it seems redundant.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/rbac Related to Role Based Access Control feature status/triage/completed Automatic triage completed status/triage/manual Manual triage in progress type/bug Something isn't working
Projects
None yet
Development

No branches or pull requests

1 participant