5.1.2.3. Users

Once authentication is set up (see Section Authentication), user administration is performed entirely within the dashboard.

Users are managed via the user management table (see Figure The dashboard user administration view.). This table lists all users known to the dashboard, including those who log in via OIDC, as well as internal and external groups added to the dashboard.

The Type column shows the kind of each entry as a colored tag. Internal users and groups have a blue tag, while users and groups found by an external authenticator (LDAP) and federated groups have a green tag. OIDC users have a purple tag that names their provider. Unmapped project users (see Section User Name and Name Mappings) have a gray tag and are hidden by default; adjust the filter of the Type column to show them. OIDC users, LDAP groups, and federated groups are read-only. The group memberships of OIDC users are provided by the OIDC provider at login and are not shown in the table.

The controls above the table add an internal user or, if an LDAP authenticator is configured, an LDAP user or group. The table can be sorted and filtered by column.

The dashboard user administration view.

The dashboard user administration view.

In addition to the user type, there are several other attributes for a dashboard user, some of which can be edited directly in the table. Editable text cells have an edit button, which opens a small dialog; flags are toggled with a checkbox.

User Mappings

The project user names shown in gray next to the username; edit them with the edit button of the cell (see Section User Name and Name Mappings)

Groups

The groups to which a user or internal group belongs; internal group memberships can be edited, LDAP group memberships are managed in LDAP

Mail

The user’s email address used for erosion notifications

Full Name

The user’s full name used for formal addressing

Password

An internal password used for authentication (usually required unless an external authenticator is used); it can be replaced or deleted

Public

Indicates whether the user is Public (see Section Public)

Disabled

Disables the account, overriding all permissions

Found in Projects

Shows projects in which the user has issues

User

Indicates whether the user may use basic functionality (see Section Permissions)

Admin

Indicates whether the user may administer the dashboard (see Section Permissions)

Project Permissions

Fine-grained, project-specific permissions for the user (see Section Permissions)

Last Activity

The time of the user’s last authenticated request to the dashboard

Internal groups can be renamed with the edit button next to their name. The username hyperlink leads to the user profile page.

Several rows can be selected with the checkboxes in the first column. The menu of the table offers the following batch operations for the selection:

Clear internal passwords

Deletes the internal passwords of the selected users. LDAP users can still log in with their LDAP password; internal users can no longer log in, and their API tokens stop working.

Reset internal passwords

Sets the internal password of each selected user to their login name.

Add default mapping

Maps each selected user without such a mapping to the project user of the same name. Selected unmapped project users become internal users with that mapping.

Add to group / Remove from group

Adds the selected users and internal groups to an internal group, which is created if it does not exist, or removes them from one.

Delete

Deletes the selected users and groups together with their permissions, memberships, and API tokens.

User Name and Name Mappings

User association is a critical step to ensure dashboard users are correctly identified as the “owners” of issues found by Continuous Integration. Since Continuous Integration only identifies users by the names provided by the project’s Version Control System (VCS), you may need to associate a dashboard user with one or more VCS names.

These associations can be flexibly configured on a per-project or project-pattern basis via the username column.

For example, suppose a company uses a company-wide LDAP for both general authentication and dashboard access. Developer “Jane White” has the ID “wjane”. If the version control system for the project “someproject” only identifies users by their real names, the analysis results will be associated with those names. The administrator can configure a mapping for the dashboard user “wjane” to the VCS user “Jane White” for all projects using the * character, provided all company projects use the same VCS. If Jane White changes her name to “Jane Doe” in subsequent commits, the administrator can add an additional mapping so that Jane owns both her old and new issues.

Since maintaining these mappings can be cumbersome, most users prefer to keep user IDs synchronized company-wide. To facilitate this, the Add default mapping for new Users option is available and enabled by default. When enabled, the dashboard assumes that the name for each user in the project databases is identical to their dashboard name. Consequently, a user created automatically (e.g., via LDAP login) will be associated with the user of the same name in the project databases. This allows project users to be looked up in an external authenticator and associated without being explicitly created as dashboard users first.

In the user management table (see Figure The dashboard user administration view.), you can configure these mappings with the edit button next to a username. By adjusting the filter of the Type column to show unmapped users in the project databases, you can map such a user to an existing dashboard user or create a corresponding dashboard user with the edit button next to the unmapped user’s name.

Public

The View Issue Owners permission (see Section Permissions) allows you to restrict whether dashboard users can see issues belonging to other users. If you choose not to grant this permission generally, you can mark specific users as Public so their issues remain visible to others.