Getting Started with Configuring Alert 6.2

When you install Alert, log in using the administrator account (sysadmin) to configure Alert.
As part of the Alert installation, you might have configured the environment variables in the Alert YAML file where you configured settings such as encryption password and global salt, authentication, or providers. If you’ve done most of the configuration, the order in which you do the configuration in the user interface might change.

Alert has the following default users that have a default password of blackduck.

• sysadmin - full system configuration access.

• jobmanager - full access to distribution jobs and read permissions for other operational functions.

• alertuser - read access for distribution jobs only.

Only the administrator has the appropriate permission to configure Alert system settings such as Settings, Authentication, User Management, or Scheduling.

The following outline is a rough guide to the order in which you might configure Alert, assuming you haven’t edited the environment variables when you installed Alert. The order is not a strict order, as it depends on your setup in terms of what you require and what you’ve configured during installation.

Navigate to the following pages from the navigation panel in Alert

1. Settings
   On the Settings page, configure the encryption password and global salt, which are required. Configure proxy settings if required. If you’ve already configured settings in the Alert YAML file as part of Alert installation, you can skip this configuration or use this feature to change settings are a later time.

2. User Management
   Configure users and roles on the User Management page.

3. Authentication
   On the Authentication page, configure LDAP and SAML users authentication if you want to add users using these authentication methods.

4. Providers
   On the Providers page, configure the Black Duck provider that provides the Black Duck notification to the configured channel such as Email or Slack.

5. Channels
   On the Channels page, configure channels such as Email or Jira that you want to use in your distribution jobs to enable the sending of notifications from the Black Duck provider.

6. Distributions
   On the Distribution page, configure distribution jobs by configuring an Alert channel and provider.
   Distribution jobs are used to process Black Duck provider notifications that are sent through channels such as Email or Slack.

7. Scheduling
   On the Scheduling page, configure scheduling of system tasks or leave at the default settings.

 

 

Open

 

Alert error messaging

The following examples denote error messages and their meaning, which you might see in the Alert user interface:

• “You are not permitted to view this information.”
  The user does not have read access to the data.

• “You are not permitted to perform this action"
  The user does not have permission to create, delete, or execute depending on the attempted action in the user interface.

• "User not authorized to perform the request"
  Pertains to the Global channel configurations such as Email, Jira Cloud, Jira Server, if the user does not have permission to save, delete, or test a configuration.

Alert security contexts

Alert 6.0.0 has the capability to add security contexts for Alert, which can be configured during installation, for example, the --security-context-file-path option is available with synopsysctl 1.0 and later where you can specify the absolute path to a file containing a map of pod names to security contexts such as runAsUser, fsGroup, and runAsGroup.

Alert volumes