Manage Security Settings
Couchbase Server security-settings can be managed from Couchbase Web Console, and by means of the REST API.
The basic settings for Couchbase security, available to Full and Security administrators, allow configuration of the following:
Users & Groups: Users and groups can be created, given passwords, and assigned roles that allow them to access specific system resources.
The Root Certificate for the node, which allows the server to identify itself to clients.
Client Certificate settings, which determine whether a client can or must present a certificate in order to authenticate with the server.
Audit settings, determining which system events are audited.
Log Redaction settings, determining what forms of content are to be considered private, and redacted from system logs.
Session management setting, whereby users are logged out of Couchbase Web Console after a specified period of inactivity.
These areas are described below.
To start managing Couchbase Server security-settings, within Couchbase Web Console, access the Security screen, by means of the Security tab, on the left-hand navigation bar:
This brings up the Security screen, which appears as follows:
Note the tabs that run from left to right, along the upper, horizontal control-bar. These are Users, Root Certificate, Client Certificate, Audit, Log Redaction, and Session. To display the corresponding screen-content for each, click on the tab:
Note also that the upper area of the screen displays notices regarding the enablement-status of saslauthd and LDAP, which can be used in support of external user-authentication. See Authentication Domains, for details.
The Users & Groups display (shown above) lists users and groups currently registered on the cluster. The display can be toggled, to provide information for either users or groups.
Each user has a username and (optionally) a full name; and can have one or more roles associated with them. These roles are themselves associated with privileges that permit access to specified system-resources. The auth domain for each user can be Local or External. To add users and, in so doing, assign them roles, administrators use the ADD USER button, at the upper right. Additionally, each user can be made a member of a defined group.
Each defined group has a group name and (optionally) a description; and can have one or more roles assigned to it. If a user becomes a member of a group, the user inherts all the group’s assigned roles. A group can also be assigned a mapping to an LDAP group that is maintained on a remote, LDAP server. For information on how Native LDAP Support can be used to support mappings, see Authorization.
A full account of adding and editing users and groups is provided in Manage Users, Groups, and Roles.
This displays the Root Certificate for the cluster:
Initially, before any administrator-driven configuration has occurred, this is a self-signed certificate. To increase system-security, a new X.509 certificate should be created.
See Configure Server Certificates, for further information.
Note that the procedures for securing Cross Data Center Replication (XDCR) may involve use of the root certificate: if so, the certificate can be copied from this screen. See Secure a Replication for details.
This displays the settings for the cluster’s handling of certificates, presented by clients attempting access:
The user interface allows the handling of client certificates to be enabled, and optionally to be made mandatory. Note that such handling is disabled by default. The Path, Prefix, and Delimiter fields allow the specification of which details within the client certificate are to be used by the server for client-identification.
This displays the audit options for the cluster:
The options permit selection of the directory within which the audit log file is to be saved, and the frequency with which it will be rotated. Specific events can also be included in the audit process, or excluded from it.
For further information, see Manage Auditing.
This allows specification of whether log files should be redacted:
A redacted log file is one purged of sensitive information: this allows log files to be shared for review purposes, without private data being compromised.
For detailed information, see Manage Logging.
This allows sessions with Couchbase Web Console to be terminated, following a specified period of user-inactivity:
For information on how to use, see Manage Sessions.