[
https://issues.apache.org/jira/browse/GUACAMOLE-248?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15935805#comment-15935805
]
Michael Jumper commented on GUACAMOLE-248:
------------------------------------------
Some sort of templating may make things easier, definitely. I'm not sure the
proper place for such things would be connection groups. Just as it's painful
to administer a large number of connections, it'd be painful to be forced to
place all related connections within a group just to reduce that aspect of the
administrative burden.
I'd say we should devote more discussion to how batch administration can be
improved in Guacamole in general before deciding on an approach.
> Support for Inheriting Connection Parameters from Group
> -------------------------------------------------------
>
> Key: GUACAMOLE-248
> URL: https://issues.apache.org/jira/browse/GUACAMOLE-248
> Project: Guacamole
> Issue Type: Improvement
> Components: guacamole-client
> Reporter: Nick Couchman
> Priority: Minor
>
> One of the things that might be nice to implement is the ability to define
> certain parts of a connection at the group level and then have those be
> inherited by the connections. The main scenario that comes to mind is that
> you want to create a balancing group of (for example) 100 RDP servers. You'd
> like all of the servers to use 3389 for the port and ${GUAC_USERNAME} and
> ${GUAC_PASSWORD} tokens for pass-through authentication from guacamole, and
> the only thing that will be different about each of the connections is the
> hostname or IP address to which they connect. The ability to define most of
> the settings on the connection group (or, perhaps, a "template connection" of
> some sort) and then allow child connections to inherit properties from either
> the parent group or template would drastically reduce the administration in
> creating at least 99 of those 100 connections.
> Seems like this involves either defining parameters at the connection group
> level, or creating a new "template" connection type that then connections
> could link to. This also seems to be fairly strictly limited to the JDBC
> authentication extension - probably not something you're going to try to do
> in either LDAP or a simple file mechanism, and JDBC is the only area where
> connection groups are supported, anyway.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
