[
https://issues.apache.org/jira/browse/GUACAMOLE-1798?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17938637#comment-17938637
]
Jerome Haas commented on GUACAMOLE-1798:
----------------------------------------
We manage multiple connection groups in Apache Guacamole where consistent
settings—such as session recording, clipboard restrictions, or timeouts—are
required across all connections within a group. Currently, we have to manually
configure these parameters for each individual connection, which is both
time-consuming and error-prone, especially when working with a large number of
connections.
The ability to define connection parameters at the parent group level and have
them inherited by all child connections would significantly reduce
administrative overhead and improve consistency. This is particularly important
in larger environments or in managed service provider (MSP) contexts, where
scaling configurations efficiently is essential.
An additional enhancement could be the ability to override inherited parameters
on specific connections if necessary, allowing flexibility while maintaining a
strong default configuration from the parent group.
I strongly support this feature and would be happy to provide further input or
testing if needed.
> Add support for connection parameter inheritance
> ------------------------------------------------
>
> Key: GUACAMOLE-1798
> URL: https://issues.apache.org/jira/browse/GUACAMOLE-1798
> Project: Guacamole
> Issue Type: New Feature
> Components: guacamole-auth-jdbc
> Reporter: bendemctl
> Priority: Major
>
> There are a lot of parameters, and those parameters are generally (at least
> for us) the same for every single connection. The only thing we change is the
> hostname and user.
> It would be great if there could be a way to avoid having to set those
> parameters over and over again and it would simplify greatly the process of
> changing those parameters (change them in the parent group instead of every
> single connection).
> I'm thinking setting connection parameters on connection groups and having
> child groups and connections inherit them (or override them) would be a good
> and intuitive way to achieve this, wdyt?
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
