Upgrading from StifleR 3.0 to 3.1

The upgrade from 3.0 to 3.1 is in-place. Install the new server over the existing installation and restart the service.

After upgrading

Set up RBAC roles

RBAC is new in 3.1. No roles exist after upgrade — you need to create them if you want to use fine-grained access control.

Your existing Global Admin and Global Read configuration (set via the Config Editor AdministratorGroup and ReadGroup settings) carries over automatically. Users in those groups will continue to have full or read-only access as before.

If you do not set up any roles, users who are not Global Admin or Global Read will be blocked at login. Create at least one role with appropriate permissions for your users before rolling out to production.

See Roles and Permissions for how to create roles and assign claim rules.

Remote Tools permissions are not migrated

In 3.0, Remote Tools had its own access control configuration. That configuration is not carried over to 3.1.

Rolling out 3.1 clients

You do not need to upgrade all clients at the same time as the server.

Scenario	Behaviour
3.0 client → 3.1 server	Works normally. 3.0 clients are unaware of the new capability endpoint and ignore it.
3.1 client → 3.0 server	Client defaults to standard mode. The 3.0 server does not support the licensing endpoint, so the client assumes no restriction is intended.

You can upgrade the server first and roll out 3.1 clients at your own pace. 3.1 clients still pointing at a 3.0 server will run in full mode — no disruption during the transition.