Documentation

9.3. Administrators¶

Administrators are dedicated to accessing the Web Manager administration service. They cannot be used for file transfer operations.

To simplify configuration management for a large number of administrators, the administrators are associated with one or more roles.

This allows, for example, to easily disable access for all administrators associated with a particular role by simply disabling the role instead of having to disable every administrator.

9.3.1. Adding a new administrator via Web Manager ¶

Administrators can be added or changed via Web Manager below.

9.3.2. Adding a new administrator via text configuration ¶

Adding a new administrator is done by creating a new section inside the configuration file. The name of the section should be prefixed with administrators/ and followed by the administrator's UUID.

The administrator's UUID can be any unique string used to identify the administrator. Once defined, the UUID should not be changed.

For more information, please see the dedicated UUID documentation.

An administrator can be an application-level account defined for accessing the Web Manager or a local operating system account belonging to an operating system group associated with a role.

For example, to add a new administrator named sa-admin:

[administrators/804aab78-70c0-4e1d-8480-4979e169a0a2]
name = sa-admin
enabled = Yes
description = Administrator account for our super admin.
password = $5$rounds=1000$utwEAUxeFBXSF0Uf$klQTAMRygQfijPXMYZCddVug
role = 404aab78-70c0-4e1d-8480-4979e169a0a4

Note

The server does not support authenticating operating system administrators that are used for multiple roles. In this case, the result is undefined.

Note

Administrator names and passwords longer than 150 characters are not allowed by SFTPPlus. Generating passwords longer than 128 characters is not possible either. These restrictions prevent denial of service attacks.

9.3.3. Options for administrators ¶

The following configuration options are available for administrators.

9.3.3.1. enabled ¶

Default value:

Yes

Optional:

Yes

From version:

2.1.0

Values:

Description:

This option specifies whether or not to enable access for this administrator.

9.3.3.2. name ¶

Default value:

Optional:

From version:

2.1.0

Values:

Any alphanumeric string including space, _ or -.

Description:

Human-readable short string used to identify this administrator.

It also represents the login or username value for this administrator.

9.3.3.3. description ¶

Default value:

Optional:

Yes

From version:

2.1.0

Values:

Any character string.

Description:

Human-readable text that identifies the person or entity to use this administrator account and/or describes the account's purpose.

Example:

[administrators/92ad5b32-d8d7-4ed8-94e1-dbb9f01383f4]
description = Administrator from the SA team.
             Contact: someone@email.tld
name = sa-operator

9.3.3.4. password ¶

Default value:

Empty

Optional:

Yes

From version:

2.1.0

Values:

Password encrypted using a one-way cryptographic hash function.
Empty.

Description:

This option specifies the password used for validating the credentials for this administrator.

It is stored encrypted using the cryptographic hash function SHA-256.

To get the hashed password please check how to generate encrypted passwords using admin-commands.

When the password is left empty, the administrator will not be able to authenticate, even if the enabled option is set to yes.

9.3.3.5. source_ip_filter ¶

Default value:

Empty

Optional:

Yes

From version:

4.14.0

Values:

Source IP/CIDR access control rules (since 4.22.0)
Empty

Description:

This option defines the access control rules based on which administrators are allowed or denied authentication.

Allowed IP/CIDR (IPv4 or IPv6) addresses are defined using access control rules, one rule per line. All rules use this format: ACTION IP-OR-CIDR

ACTION is any of the following values:

allow - allows access from IP or CIDR
deny - denies access from IP or CIDR

The administrator configuration option is similar to the account configuration. For more details, see the account configuration documentation page.

For examples of how to use the access control rules see the authentication documentation page.

9.3.3.6. multi_factor_authentication ¶

Default value:

Empty

Optional:

Yes

From version:

4.0.0

Values:

OTP Authentication URL
Empty.

Description:

This option specifies the One-Time Password shared secret associated with this administrator, stored as an otpauth:// URL, as defined by the Google Authenticator

More information on 2-step authentication is available on the cryptography guide page.

9.3.3.7. roles ¶

Default value:

DEFAULT-ROLE

Optional:

From version:

4.16.0

Values:

UUID of a role.
Comma-separated UUID of roles

Description:

This option defines the roles associated with this administrator.

It can be configured with one or multiple role UUIDs.

The first UUID is the primary role of this administrator.

Updating this configuration doesn't impact the sessions of already authenticated administrators, which continue to use the old configuration value. The new value is only used for new authentications.

9.3.3.8. node_variables ¶

Default value:

Empty

Optional:

Yes

From version:

2.26.0

Values:

INI text

Description:

This is designed to be used when this administrator is used to synchronize the configuration to a remote node.

The value from here is used to overwrite any configuration when applied to the remote node.

9.2. Groups

9.4. Roles