After installing an update to the BSUS app - Adaptive Applications - BlueCat Gateway - 22.1

BlueCat Server Update Services Administration Guide

English (United States)
Product name
BlueCat Gateway

After installing a BSUS update, you might be required to restart the BSUS app. When a BSUS update is ready to be finalized, BSUS displays a red banner at the top of the screen warning you that BSUS needs to restart. To do so, click the Update button in the banner. The restart and final installation should take only a couple of seconds.

Some of the changes in the latest versions require additional actions after the update is installed. If you're updating the BlueCat Server Update Services app itself from a version prior to the listed version, you may need to perform additional setup or configuration.

Update BSUS on BDDS servers

(Update to: any update)

After successfully installing a BSUS update, you might need to also update the parts of the BSUS app that live on the DNS servers that it manages. To do so:
  1. Go to the main BSUS dashboard (click Dashboard), then click the tabs for each of the Server Batches you work with.
  2. Within each tab, a DNS server that needs to be updated with a new BSUS version will be tagged with an arrow and red circle ().

    To update a server, click its red arrow.

Note: We recommend you first update the main BSUS application (click the Update button in the red banner) before updating any DNS servers.

Add DB_SEARCH to environment (.env) settings

(Update to: BSUS v22.1)

The BSUS database can now be password-protected for greater security. After you update the BSUS app, within the BSUS .env file, make sure that you specify the password for your search database.

To do so, make sure you configured the following new setting within the .env file:

where MyPassword is your chosen password for the search database.

Note: Until you specify a password in the .env file, the search database will be unprotected. If no password is set on the database, BSUS will set the database password the first time it sees the DB_PASSWORD setting in the .env file.

If the database is already password-protected, BSUS will attempt to use the password specified in DB_PASSWORD. Therefore, after adding DB_PASSWORD to the .env file, do not change it again.

Configure BSUS for TLS 1.2 encryption

(Update to: BSUS v22.1)

As of version 22.1, BSUS will use TLS (Transport Layer Security) 1.2 encryption when communicating with BDDS servers and optionally between BSUS docker containers. These communications require the use of security certificates. They also require an additional port (10046) to be opened between BSUS and the BDDS servers it manages.

For more details on setting up TLS encryption for BSUS and the BDDS servers, see Configuring BSUS for TLS encryption.