Load balancing
The PassMan Cluster configuration can also operate in a load balancing mode, when inactive members can also be used for daily work.
The advantage of this is that there is no need to allocate additional resources for the possible expansion of the PassMan primary (VIP) node.
Prerequisite:
Existing Load Balancer (not part of PassMan)
Load balancer settings:
- PassMan nodes must be added (Only 3 node addresses. VIP node should not be configured!)
- Session retention must be set
The operational status of the node can be tested by making a GET request to the <PassMan node IP address>/padmin/api/node_availability_code API.
If a node is working properly, a number 200 response will be returned.
In the case of the following errors, users cannot use the specified node:
- In case of error 511, the Safe is locked, and any user connected to it cannot work in Passman
- In case of error 502, PassMan is not running on the given node, therefore it cannot be used
- In case of error 503, the database is not usable, therefore the system cannot be used
PassMan settings:
On each node that we want to use, the Safe must be opened by connecting via the unique node IP.
Using Padmin
To connect (mostly to see logs on specified nodes), the unique IP address of the node must be used (NOT via the load balancer)