Roles (RBAC)
This page describes StackState version 4.0.
The StackState 4.0 version range is End of Life (EOL) and no longer supported. We encourage customers still running the 4.0 version range to upgrade to a more recent release.
Every user in StackState needs to have a subject and a set of permissions assigned; this combination is called a role. A role describes a group of users that can access a specific data set. This instruction will take you through the process of setting up a new group called “StackState Manager”.
Subjects need two pieces of information: a subject name and a subject scope. Create a new subject - set it’s name to
stackstateManager
and set the scope to'label = "StackState" AND type = "Business Application”’
as in the following example:Please note that when passing an STQL query in a CLI command, all operators (like
=
,<
,AND
, and so on) need to be surrounded by spaces, as in the above example.Also, please note that the subject's name is case sensitive.
Configured subjects need permissions to access parts of the UI and to execute actions in it. StackState Manager role requires access to the specific view of business applications, and there is no need to grant any CRUD, or StackPack permissions - they will not be used in day-to-day work by any Manager. To grant permission to view the
Business Applications
view, follow the below example:Please note that the subject's name, as well as permissions, are case sensitive.
Finalize setting up roles for the file-based authentication
If your StackState instance is configured with a file-based authentication, then you need to add newly created subjects to the config file and enable authentication.
In the
application_stackstate.conf
file locate theauthentication
block and changeenabled = false
toenabled = true
as in the below example:Add new users and subjects to the
logins
table in theapplication_stackstate.conf
as in the following example:
Last updated