Authentication options

Out of the box, StackState is configured with file-based authentication with a default username and password. This authenticates users against a file on the server. However this is not a production-ready setup.

For better security StackState can be configured to use exactly one of the following authentication mechanisms (replacing the standard admin user):

  • Kubernetes authentication configuration is part of the Helm chart, any changes will automatically triger a restart of the pods requiring that.

  • Linux authentication configuration is stored in the file etc/application_stackstate.conf in the StackState installation directory. Restart StackState for any changes made to this file to take effect.

User roles

When a user has been authenticated permissions for that user are usually assigned based of the roles the user has. The documentation for the specific authentication mechanisms also contain examples on how to map the roles or groups from the external systems to the 3 standard roles of StackState:

  • Guest - able to see information but make no changes.

  • Power User - able to see and change all configuration and install StackPacks.

  • Administrator - able to see and change all configuration, install StackPacks, grant and revoke user permissions and upload (new versions of) StackPacks.

When deciding on the roles to assign your users it is strongly advised to have only a small group of Administrators, for example only the engineers responsible for installing StackState and doing the initial configuration. Administrator users can manage access to StackState and decide which StackPacks can be used. Installing StackPacks and other fine tuning of the configuration can be delegated to a larger number of users with the Power User role.

It is also possible to add more roles, see the page Roles (RBAC) and the other RBAC documentation pages​