As of v25.1, you can set up Gateway to authenticate users without connecting to Micetro or Address Manager server. This lets you use the Gateway platform to automate tasks even if your infrastructure does not use Micetro or Address Manager.
To set up Gateway with standalone authentication, you must have the following:
-
BlueCat Gateway v24.0 or greater
-
Docker engine
Gateway supports three types of authentication platforms: Address Manager, Micetro or Gateway Standalone authentication. Authentication with Address Manager or Micetro is recommended in most cases. Note that a single Gateway server can be configured to use only one type of authentication.
Like Micetro or Address Manager authentication, standalone Gateway authentication supports logins from both the UI and the Gateway REST API. Gateway performs all management of Gateway user sessions.
When using Standalone authentication, by default, Gateway itself authenticates credentials. Standalone authentication works as follows:
You can set up one (and only one) administrator user (belonging to the built-in Admin Gateway group) to be authenticated by Gateway.
This user's username and password are stored in memory in the Gateway container process as container environment variables. After installation, the username and password cannot be changed: To change these credentials, you must delete and reinstall the container image.
This default Standalone setup is a simple deployment intended for applications that do not need to support many users, since you do not need to install Address Manager or Micetro (which have significant disk space and memory requirements and can be complex to configure).
You can override the default Standalone authentication with custom authentication code. Doing so is useful for workfow developers who want to build workflows that need to authenticate multiple users, but do not need or want Address Manager or Micetro.
Custom authentication code is stored in the same location as built-in Gateway workflows and (like built-in workflows) can be used only by Gateway. It requires that the Gateway container image be re-built containing that code.
- For details on changing the Standalone authentication user credentials, see To change the username and password for the default user when using Standalone authentication.