Chat now with support
Chat with Support

syslog-ng Store Box 6.0.5 - Administration Guide

Preface Introduction The concepts of SSB The Welcome Wizard and the first login Basic settings User management and access control Managing SSB Configuring message sources Storing messages on SSB Forwarding messages from SSB Log paths: routing and processing messages Configuring syslog-ng options Searching log messages Searching the internal messages of SSB Classifying messages with pattern databases The SSB RPC API Troubleshooting SSB Security checklist for configuring SSB Glossary

Managing SSB users locally

By default, SSB users are managed locally on SSB. In order to add local users in SSB, all steps of the following procedure need to be completed:

  1. Create users.

    For detailed instructions on how to create local users, see Creating local users in SSB.

  2. Assign users to groups.

    For details about how to add a usergroup, see Managing local usergroups.

  3. Assign privileges to groups.

    For information on how to control the privileges of usergroups, see Managing user rights and usergroups.

Creating local users in SSB

This section describes how to create a local user in 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.

To create a local user in SSB

  1. Navigate to AAA > Local Users and click .

    Figure 45: AAA > Local Users — Create local user

  2. Enter the username into the User field.

    		 NOTE:

    The following characters cannot be used in usernames: <>;\/[]:|=,+*?

  3. Enter a password for the user into the Password and Verify password fields.

    		 NOTE:

    SSB 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.

  4. 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.

  5. Click Commit.

Deleting a local user from SSB

This section describes how to delete a local user from SSB.

To delete a local user from SSB

  1. Navigate to AAA > Local Users.

  2. Find the user you wish to delete.

  3. Click next to the user, at the right edge of the screen.

  4. Click Commit.

Setting password policies for local users

SSB 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.

This section describes how to create a password policy.

To create a password policy

  1. Navigate to AAA > Settings.

    Figure 46: AAA > Settings > User database — Configure password policies

  2. 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), then SSB manages the passwords of the admin and root users locally.

  3. 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.

  4. 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.

  5. 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 entropy: the variety of numbers, letters, capital letters, and special characters used, not only by its length. A strong password must have at least 12 characters, including lowercase and uppercase letters, numbers, and special characters.

    The Enable cracklib option executes some simple dictionary-based attacks to find weak passwords.

  6. Click Commit.

    		 NOTE:

    If you increase the Minimal password strength, users whose existing password is weaker than required 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.

Related Documents

The document was helpful.

Select Rating

I easily found the information I needed.

Select Rating