Functional Administration on oPBWeb Manual

Users and Roles

Mon, 01 Jan 0001 00:00:00 +0000

Role: Administrator

Overview

Under Users and roles, you manage all accounts that can sign in to oPBWeb. Each account has exactly one role, which defines what it may do in the UI. Besides local accounts that you create yourself, there are directory accounts from LDAP whose role is derived from their groups in the directory.

Open the area with the Users and roles icon at the bottom of the activity bar. It has two tabs: Users (with the number of accounts) and Audit log. The audit log is described in the Audit log chapter.

Audit Log

Mon, 01 Jan 0001 00:00:00 +0000

Role: Administrator

Overview

The audit log records who triggered which important action in oPBWeb and when: sign-ins and changes to accounts, packages, depots and settings. You find it under Users and roles on the Audit log tab. Only administrators can read it.

Entries can be neither changed nor deleted in the UI. Even if you delete a user account, its entries are kept with the user name.

Reading the audit log

Config Servers

Mon, 01 Jan 0001 00:00:00 +0000

Role: Administrator

Overview

oPBWeb works with any number of opsi config servers, for example a test, a staging and a production system. Through each config server, oPBWeb reads its depots, installs packages and accesses /repository, /workbench and /depot. Each depot belongs to exactly one config server.

You manage the config servers in the Depots view in the activity bar. As long as no config server is configured, depots, installing and the workbench do not work, and the status bar shows “No config server configured”.

Settings for New Packages

Mon, 01 Jan 0001 00:00:00 +0000

Role: Administrator

Overview

Under Settings, you define the values new packages and meta packages start with, and which mail address changelog entries get when the user has no email. The values apply to all users. Only administrators may change them.

The defaults only take effect when a package is created. Existing packages and imported packages (.opsi or workbench) keep their own values, and every Packager can override the defaults in the package editor.

Depot Management

Mon, 01 Jan 0001 00:00:00 +0000

Role: Administrator

Overview

oPBWeb reads the list of depots from the configured opsi config servers. Each depot belongs to exactly one config server. As an administrator, you define for each depot which Stage it runs in, which Service URL oPBWeb uses to reach it and whether it is used at all (Enabled). The stage determines which role may install on the depot.

You find these settings under Depots. The list on the left is grouped by config server: each config server is shown as a bold row, with its depots indented below it, each with a stage badge and the number of products; for the config server’s own depot, for example, “config server · 120 products”. Additions such as “disabled” or “no longer present” also appear in the second line. How to add and maintain config servers is described in Config servers .

System Status

Mon, 01 Jan 0001 00:00:00 +0000

Role: Administrator

Overview

The System status area shows whether all oPBWeb services are running and gives administrators insight into how the database and object storage are used. Open it with the System status icon at the bottom of the activity bar.

All roles see the services table. Only administrators see the Database, Object storage (with Clean up …) and Bucket contents sections.

Functional Administration on oPBWeb Manual

Users and Roles

Overview

Audit Log

Overview

Reading the audit log

Config Servers

Overview

Settings for New Packages

Overview

Depot Management

Overview

System Status

Overview

Checking services