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.

Sign up for GitHub

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

Jump to bottom

Override security per connection #710

Closed
sverrehu opened this issue May 26, 2021 · 2 comments
Closed

Override security per connection #710

sverrehu opened this issue May 26, 2021 · 2 comments
Labels
acl Kafka ACLS enhancement New feature or request

Comments

@sverrehu
Copy link
Contributor

sverrehu commented May 26, 2021 •
edited
Loading

We use AKHQ to let anonymous (micronaut.security.enabled: false) users inspect two clusters/connections. We have set akhq.security.default-group to refer to a group that has the roles we wish to give our users.

In one of the clusters, AKHQ has no access to topic data, while in the other cluster AKHQ has unlimited access.

We would like to configure AKHQ to reflect this, ie. allow topic/data/read in only one of the clusters. When browsing the README.md, I get the impression that this is not currently possible.

So this is an RFE: Allow akhq.connections.foo to have a security key for overriding the global akhq.security. Or otherwise make it possible to specify a default-group per connection.
@tchiotludo
Copy link
Owner

Not possible for now, look at this for more insight : #523

@tchiotludo tchiotludo added acl Kafka ACLS enhancement New feature or request labels May 26, 2021
@tchiotludo
Copy link
Owner

done in #1472

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
acl Kafka ACLS enhancement New feature or request
Projects
Backlog
Status: Done
Milestone
No milestone
Development

No branches or pull requests
2 participants
@tchiotludo @sverrehu