The following describes how to create a local user in syslog-ng Store Box (SSB).
NOTE: The admin user is available by default and has all possible privileges. It is not possible to delete this user.
Local users cannot be managed when LDAP authentication is used (see Managing SSB users from an LDAP database). When LDAP authentication is enabled, the accounts of local users are disabled, they are not displayed on the AAA > Local Users page, but they are not deleted, either.
When using RADIUS authentication together with local users, the users are authenticated to the RADIUS server, only their group memberships must be managed locally on SSB. For details, see Authenticating users to a RADIUS server.
When using OpenID Connect authentication together with local users, the users are authenticated via OpenID Connect, only their group memberships must be managed locally on SSB. For details, see Authenticating users via OpenID Connect.
To create a local user in SSB
-
Navigate to AAA > Local Users and click 
.
Figure 73: AAA > Local Users — Create local user
-
Enter the username into the User field.
NOTE: The following characters cannot be used in usernames: < > ; \ / [ ] : | = , + * ?
-
Enter a password for the user into the Password and Verify password fields.
NOTE: The syslog-ng Store Box (SSB) appliance accepts passwords that are not longer than 150 characters. The following special characters can be used:
! " # $ % & ' ( ) * + , - . / : ; < > = ? @ [ ] ^ - ` { | } \ _ ~ |
The strength of the password is indicated below the Password field as you type. To set a policy for password strength, see Setting password policies for local users. The user can change the password later from the SSB web interface, and you can modify the password of the user here.
-
Click in the Groups section and select a group that the user will be member of. Repeat this step to add the user to multiple groups.
If you wish to modify the group membership of a local user later on, you can do that here.
To remove a user from a group, click 
next to the group.
NOTE: Attempting to log in with a local user that is not a member of any Groups will automatically result in authentication failure. Login failures of such users will count to the automatic user lock feature limit. For information on creating Groups and setting Groups for a local user, see Creating local users in SSB and Managing local usergroups.
-
Click 
.
This section describes the automatic user lock feature of syslog-ng Store Box (SSB) and how to lock or unlock a local user manually on SSB.
Automatic lock of user after authentication failure
The SSB appliance will automatically lock a local user after three authentication failures via RPC API or the webUI in a 15-minute time period.
NOTE: The local user admin cannot be locked.
NOTE: Attempting to log in with a local user that is not a member of any Groups will automatically result in authentication failure. Login failures of such users will count to the automatic user lock feature limit. For information on creating Groups and setting Groups for a local user, see Creating local users in SSB and Managing local usergroups.
To manually lock or unlock a local user on SSB
-
Navigate to AAA > Local Users.
Figure 74: AAA > Local Users — Lock/unlock local user
-
Find the user you want to lock or unlock.
-
To lock or unlock a user, select or clear the check box in the Locked column next to the user.
NOTE: The local user admin cannot be locked.
-
Click Commit.
This section describes how to delete a local user from syslog-ng Store Box (SSB).
To delete a local user from SSB
-
Navigate to AAA > Local Users.
-
Find the user you wish to delete.
-
Click next to the user, at the right edge of the screen.
-
Click .
The syslog-ng Store Box (SSB) appliance can use password policies to enforce minimal password strength and password expiry. Password policies apply only to locally managed users, including the built-in admin and root users. They have no effect on users managed from an LDAP database, or if you authenticate your users to a RADIUS server or via OpenID Connect.
The following describes how to create a password policy.
To create a password policy
-
Navigate to AAA > Settings.
Figure 75: AAA > Settings > User database — Configure password policies
-
Verify that the Authentication method is set to Password provided by database and that the User database is set to Local.
NOTE: If the setting of these fields is different (for example LDAP or RADIUS or OpenID Connect), then SSB manages the passwords of the admin and root users locally.
-
Set how long the passwords are valid in the Password expiration field. After this period, SSB users will have to change their password. To disable password expiry, enter 0.
-
To prevent password-reuse (for example, when a user has two passwords and instead of changing to a new password only switches between the two), set how many different passwords the user must use before reusing an old password.
-
To enforce the use of strong passwords, select the level of password-complexity from the Minimal password strength field. As you type, SSB shows the strength of the password under the password field.
NOTE: The strength of the password is determined by its length and entropy (the variety of numbers, letters, capital letters, and special characters used). A strong password must have at least 12 characters, including lowercase and uppercase letters, numbers, and special characters. The Strict level has a minimal password length selectable in the range of 15-35 characters.
The Enable cracklib option runs some simple dictionary-based attacks to find weak passwords.
When the Minimal password strength field is set to Strong or Strict, altering at least 8 characters is mandatory when changing a password. This refers to the number of changes required with respect to the total number of positions in the current password. In other words, characters may be the same within the two passwords. However, the positions of the identical characters must be different.
-
Click .
NOTE: If you increase the Minimal password strength or the Minimal password length settings in case of a Strict minimal password strength, users whose existing password does not match the requirements are forced to change their passwords immediately after their next login. The new passwords must comply with the strength requirements set in the password policy.
