Users and administrators

Accounts come from one of two places:

• Built-in accounts, kept by Casvisor itself. This is the default, used whenever casdoorEndpoint is empty.
• Casdoor, when casdoorEndpoint is set. Casvisor then keeps no accounts of its own; see Connect Casdoor.

Either way, what a signed-in user may do depends on one question: is this user an administrator?

Built-in accountsCopy Anchor Link

On first start, when there are no users yet, Casvisor creates the administrator admin. Its password is adminPassword from the configuration, or a random one printed once in the log; see Quick start.

Administrators manage accounts under Users:

The last administrator who can sign in cannot be deleted, forbidden or have Is admin taken away, so Casvisor never ends up without one. Nobody can sign up by themselves.

Everyone changes their own password under My Account, in the menu at the top right. Passwords are stored as bcrypt hashes. After 5 wrong passwords for a user from one address, sign-in for that user from that address is refused for 15 minutes; other addresses are not affected, so nobody can lock an administrator out from elsewhere.

All built-in accounts belong to one organization, named by casdoorOrganization, casvisor by default. Changes to a user, such as new groups or Is forbidden, apply at once, to the web UI and to open sessions alike.

AdministratorsCopy Anchor Link

A user is an administrator when Is admin is on for them: under Users for built-in accounts, or in Casdoor, which makes them an administrator of their Casdoor organization. With Casdoor, users of Casdoor's built-in organization are administrators too.

Administrators:

• see Users (built-in accounts only), Network gateways, Permissions, Patches, Sessions, Commands, Command rules and Records (the operation log), and manage Assets;
• can connect to every asset of their organization, with every action, without a permission;
• can stop anyone's session, watch it live and replay its recording.

An administrator of one organization cannot manage the assets or permissions of another. Users of Casdoor's built-in organization can, which is why they should be few.

Everyone elseCopy Anchor Link

Users who are not administrators:

• land on the workbench, which lists only the assets a permission gives them Connect on;
• can call only the API needed to list those assets, connect to them, move files in their own sessions, and manage their own SSH keys;
• cannot see stored passwords, other people's sessions, recordings, the command records, or the operation log.

A user with no permission at all signs in to an empty workbench.

Limiting who can sign inCopy Anchor Link

By default every user can sign in: every built-in account, or every user of the Casdoor application's organization. Those without permissions get an empty workbench. To let only certain users in at all, set allowedUsers to a comma-separated list of organization/name, such as my-org/alice,my-org/bob. Anyone else is turned away at sign-in.

GroupsCopy Anchor Link

With built-in accounts, groups are what you enter under Users. With Casdoor, Casdoor's groups carry over: the token Casdoor issues at sign-in lists the user's groups. Either way, a permission that names a group applies to every member.

When changes in Casdoor take effectCopy Anchor Link

Casvisor reads the user's groups and administrator flag from the token it gets at sign-in, and keeps that sign-in until the user signs out or the browser session ends. Adding someone to a group, removing them, turning Is admin on or off, or disabling the user in Casdoor therefore applies to the web UI the next time they sign in to Casvisor, not at once.

The SSH gateway has no web sign-in: it reads the user from Casdoor at every connection, so a disabled or deleted user cannot open a new gateway connection from then on. A connection already open keeps the groups it started with.

To cut someone off now:

1. Take them out of the permissions that name them, or turn those permissions off. This also refuses them at the SSH gateway, whatever keys they have registered, and their open sessions to the assets those permissions gave them are disconnected straight away; see Disconnected when the permission goes.
2. Stop any session that is still open under Sessions.

Signing out of Casvisor ends its own cookie only. It does not sign the user out of Casdoor, so the next visit may go through without a password, as with any single sign-on.