Address Manager v25.1 support
This release supports BlueCat Address Manager v25.1, the newest release of BlueCat Integrity X.
Updated look and feel
The v25.2 release features a complete revision of the Gateway UI. This revision aligns the Gateway user interface with new user experience standards established by BlueCat Address Manager v25.1. The new user experience is smoother, cleaner, and more intuitive. This release contains the same features as previous versions, but with improved usability and presentation.
Gateway platform API updates
This release of Gateway includes the following API updates.
- Python functions in the server_endpoints and util modules have been updated to use the Address Manager REST API specified for the local Gateway instance. Previously, these functions used only the Address Manager REST V1 API regardless of how Gateway was configured. As of v25.2, these functions will now use the Address Manager REST API that is configured for that instance of Gateway (either the Address Manager REST V1 API or Address Manager REST V2 API).
-
The function get_host_record_data() was added.
-
The following functions were updated:
- get_view_data()
- get_views_endpoint()
- get_zones_data_by_hint()
- get_zones_endpoint()
- get_address_data()
- get_ip4_address_endpoint()
- get_host_record_data()
- get_host_records_endpoint()
- get_alias_record_data()
- get_alias_records_endpoint()
- get_text_record_data()
- get_text_records_endpoint()
- config_filter()
Configuring multiple BlueCat Address Managers on startup of Gateway container via the command line
As of BlueCat Gateway 25.2, the Gateway container image is built using the Debian Bookworm operating system, upgraded from Debian Bullseye version.
As part of this upgrade, the version of Python used in Gateway that comes with Debian has been upgraded to Python v3.11 (from v3.9).
We recommend that any custom workflows built to run in previous versions of Gateway that you wish to run in Gateway 25.2 (or future versions) be retested with Gateway 25.2 to ensure they function correctly before going into production. Workflows written using Python 3.9 may not be compatible with Python 3.11 and will require code changes.
Debian Bookworm OS upgrade
As of BlueCat Gateway v25.2, you can now specify multiple Address Manager servers when deploying Gateway. In the login screen, users can then select from all specified servers.
Default flask user used when running Gateway container is no longer assigned root group privileges
The Gateway container is built on the Debian operating system image. It comes
with a user named flask, which was previously assigned to
be a part of the Debian root group. As of the Gateway 25.2
release, the flask user is now assigned to a new group defined in the
Gateway image called flaskgroup, which is a non-root
group.
This change lets the Gateway container run under a non-root user
(flask) with a non-root group. The Apache server
process inside the container will also run under this user and group. This
change enhances security by following the least privilege principle, making
sure that the Gateway container is run with as few privileges as
possible.