Scopes
This page describes StackState v4.4.x.
The StackState 4.4 version range is End of Life (EOL) and no longer supported. We encourage customers still running the 4.4 version range to upgrade to a more recent release.
How do scopes work?
The scope is an STQL query that is added as a prefix to every query executed in StackState. Whenever a user wants to select a view or pass a query in StackState, this prefix query is executed as a part of the user's query, limiting the results accordingly to the user's role.
Note: Please note that function calls like withCauseOf and withNeighborsOf are not supported as they would not be performant in this context.
If a user belongs to multiple groups, then this user can have multiple scopes, which translates to multiple prefixes. In this situation, the prefix is executed as an OR of all scopes that this user has.
Users need to log out and authenticate again to StackState whenever any changes to roles or permissions are made.
Why scopes?
Scopes are introduced as a security feature that is mandatory for every subject within StackState. The predefined StackState users Administrator, Power User and Guest roles have no scope defined.
It is possible to provide a scope as a query wildcard, however, this will result in access to everything and is not recommended. If there is a need for access without a scope, it is recommended to use one of the predefined roles instead.
Examples
The below example shows the same topology view called "All Infrastructure" for four users with different permission levels.
This user is a part of StackState Admin group, so there is no scope:
The query for this view is the same as for the others, but without any prefix:
Below user is in a group with configured subject X with the following scope:
Query with the prefix for this view is:
Another user who is a part of a group with a configured subject Y that has the following scope:
gets this topology:
Query with the prefix for this view is:
User with multiple prefixes
It is possible to assign a subject to more than just one group. In this example, you can see an Infrastructure Manager who can see the whole view presented above. This user has to be in both groups that have configured subjects as X and Y. In this case, the prefix for the user query will look like the following:
Query with prefix for this user is then:
Which results in a following view:
Last updated
