Skip to content

GateKeeper v.1.5.x

Blackwall GateKeeper is a protective reverse proxy built on Blackwall’s bot and hacker detection technology. Just like our core software platform, you can choose to use the UI described in this section, or if you are looking for information about the associated API, refer to the latest General Availabilty version of GateKeeper API Guide.

To implement and use GateKeeper via the user interface (UI), refer to GateKeeper Quick Start

Release Notes v1.5.x

Release Notes v1.5.0

The following are release notes for the Blackwall GateKeeper v1.5.0 release. A number of features were added, enhancements made, and issues fixed to improve the platform. Notably, the GateKeeper API is now generally available (GA) following extensive improvements based on beta feedback, and the version numbers of both the API and UI have been unified for consistency across the product suite.

Features and Enhancements:

  • GateKeeper API:
    • Blackwall is pleased to introduce the first General Availability (GA) version of our application load-balancing GateKeeper API, with support for multi-tenant management. This API provides hosting partners, SaaS users, and integration developers with a programmatic interface to manage users, websites, and settings. This mirrors all key features available in the Blackwall dashboard. It also supports a reseller model, with master and sub-account hierarchies for scalable, delegated access. Significant enhancements have been made to the beta version previously released to a limited user group and feedback provided has been incorporated into this GA version. For example, a website custom rules API editor has been added, and the ability to get event logs for all Gatekeeper API schemas (user, device, server, website). (Closes GK-41)
    • A new feature has been added, introducing read-only event log API endpoints for users, devices, servers, and websites. This feature adds support for retrieving event log record via new GET endpoints, enabling clients to fetch event data scoped to specific resources; for example, /user/{user_id}/events, or /device/{device_id}/events. The API supports filtering by time range and other rule-based parameters, providing flexible access for auditing, analysis, and integrations. (Closes GK-184)
    • Added a possibility to get event logs for all Gatekeeper API schemas (user, device, server, website). (Closes GK-136)
  • Authentication: Logout functionality has been added to the GateKeeper dashboard. Similar to the BotGuard dashboard, users can now securely log out of the GateKeeper UI. This feature enhances session control and aligns authentication behaviour across the Blackwall platform. (Closes GK-139)
  • User Experience: Added support for light mode in the GateKeeper platform UI, enabling users to toggle between dark mode and light mode based on personal visual preference or environment. Previously, only dark mode was available. (Closes GK-58)
  • Infrastructure: A new 'Early Hints' feature has been added to help users optimize their websites, whether using the Blackwall GateKeeper user interface (UI) or our GateKeeper API. HTTP header 103 support has been added along with the corresponding web application acceleration logic, by implementing a module for nginx and using it in GateKeeper. This added feature significantly improves browser page load performance, leading to a smoother browsing experience. (Closes GK-51)

Fixed Issues:

  • Infrastructure: The nginx-stat-module has been replaced with the status-nginx-module to prevent OOM crashes during frequent Nginx reloads. By replacing it with the more stable status-nginx-module, GateKeeper now supports safe and reliable configuration reloads, even under high-frequency update cycles. (Closes GK-144, GK-199, and GK-138)
  • GateKeeper API: A fix has been created for an issue preventing domains without IPv6 addresses from being added via API. Previously, domains that only had IPv4 (or only IPv6) addresses were incorrectly rejected when added through the API. This fix correctly distinguishes between a missing IPv6 address and an invalid one, allowing valid domains with single-stack configurations to be registered and function as expected. (Closes GK-195)
Feedback