Question Regarding Show/Hide Clusters and Specific Topics #2136
-
|
We have two clusters that are connected to AKHQ using one UI, I would like to know if there is the possibility of showing specific Clusters depending on Roles (Example Topic-Reader just seeing Cluster1). Additionally, is there a way to hide specific topics, perhaps via regex to specific roles? Thanks in advance. |
Beta Was this translation helpful? Give feedback.
Replies: 2 comments 7 replies
-
|
Yes for both of your questions. You can check here:https://akhq.io/docs/configuration/authentifications/groups.html The groups definition allows you to define a mapping between roles, patterns (regex for topic names, subjects names, consumer groups, etc. - all the different resources types managed in AKHQ) and clusters. You will find some examples here |
Beta Was this translation helpful? Give feedback.
-
|
Good Morning @AlexisSouquiere thank you for your reply! I have a follow-up question, so this is our configuration: As you can see for the topic-reader I've applied a regEx topic filter, that will basically NOT show anything that has 'cdc' in the topic name. This works, however, since I am a member of each group, I still get effected by this. With regards to the clusters - this is how I tried to implement it: where in my connections configuration I have the following: |
Beta Was this translation helpful? Give feedback.
-
|
I think you are using a version <= 0.23.0 which only proposed a partial RBAC implementation. Try with the latest version and update the groups / roles accordingly |
Beta Was this translation helpful? Give feedback.
-
|
Sorry I wanted to say <= 0.24.0. The new RBAC implementation was released in 0.25.0 |
Beta Was this translation helpful? Give feedback.
-
|
In 0.25.0, lets say a member is part of each group, will the highest group take over? I.E. Will it fix my current situation? |
Beta Was this translation helpful? Give feedback.
-
|
With 0.25+ you will have to rewrite the groups definition. Adding topic-related permissions in a consumer groups group without any restrictions makes no sense. Permissions will be fine-grained for each resource types |
Beta Was this translation helpful? Give feedback.
-
|
And one final question, lets say we have to stick with the current version, if I had to have a user being ONLY in 1 group, in this case the 'admin' group, that user will not be effected with the attribute filter correct? As long as each user is only part of one group. Thank you for all the help! |
Beta Was this translation helpful? Give feedback.
-
|
Yes, correct. Filters are applied only to the group on which it's defined |
Beta Was this translation helpful? Give feedback.
Yes for both of your questions. You can check here:https://akhq.io/docs/configuration/authentifications/groups.html
The groups definition allows you to define a mapping between roles, patterns (regex for topic names, subjects names, consumer groups, etc. - all the different resources types managed in AKHQ) and clusters.
You will find some examples here