Authorization
Authorization
WARNING
This configuration will be deprecated in version 1.9 and removed in the future. In version 1.9 this configuration will be used to preload user groups and based on that create permissions for each group.
Authorization
Kouncil enables restricting access to pages and functions. To achieve that you should add appropriate properties to your configuration file. There are three: kouncil.authorization.role-admin
, kouncil.authorization.role-editor
, andkouncil.authorization.role-viewer
. Each one of these allows users to do specific actions in Kouncil. Users with roles assigned to:
kouncil.authorization.role-admin
can view brokers and consumer groups pageskouncil.authorization.role-editor
can view topics, event tracker pages, and send messages to topicskouncil.authorization.role-viewer
can only view topics and event tracker pages
As a value in these parameters you should provide a list of groups defined in the selected authentication provider (inmemory
, LDAP
, AD
, SSO
), separated by a semicolon (;
).
For the default configuration, we have defined the user groups:
These will be used in any authentication method unless you override them in any of your configuration files used by Kouncil.
Example of role configuration:
To get LDAP user groups in LDAP configuration, add a few additional parameters (group-search-base
, group-search-filter
, group-role-attribute
)
Configuration
Since version 1.9 configuration of user groups and user groups permissions is available from UI.
When permissions will change users will see the message that re-login is required.
By default, users with groups assigned to kouncil.authorization.role-admin
will be able to manage user groups and user groups permissions.
Last updated