This isn't perhaps exactly what you're looking for, however it may
contain some useful information?:
https://lists.apache.org/thread/mt313c64nmfwnzhl61g0brwm8g9gq3z9
On 31/07/24 17:35, M Anon wrote:
Hi,
Tried searching in the archives for "redundancy", "failover" and "high
availability" but got no hit.
What we'd like to achieve is to have 2 servers but at any time we can
take one offline (for patching / maintenance, etc). We are OK with users
being disconnected and having to reconnect to the other server but what
we don't want is to have to configure each user on both servers' database.
We authenticate users via LDAP and we know that we can store connection
info in AD by modifying the schema but we'd rather avoid touching the
schema. Can we utilize the ability of database authentication where
users are auto-provisioned in the database if successfully authenticated
by LDAP? How do we specify different groups of connections for each user
if they are auto provisioned e.g.:
Group A - IT has access to all servers via RDP and SSH
Group B - student group 1 has access only to APPSERVER1 via RDP
Group C - student group 2 has access to APPSERVER1 and APPSERVER2 via RDP
Group D - contractor 1 has access to only APPSERVER1 via SSH
and so on ...
Any tips are appreciated ...
PS: not sure it will matter (I don't think so) but we do have a HTTP/S
balancer that will sit in front of the 2 Guac servers
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
