[
https://issues.apache.org/jira/browse/GUACAMOLE-248?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16099474#comment-16099474
]
Michael Jumper commented on GUACAMOLE-248:
------------------------------------------
{quote}
I'm guessing we want the batch administration discussion on the mailing lists,
and not just here in JIRA
{quote}
Yep.
{quote}
user list, dev list, or both?
{quote}
You never want to open identical threads on multiple lists - that only leads to
confusion and missed responses. For discussing things at a high level, without
getting into implementation details, the user list would be best. Once we have
a good idea on the high level changes that would be best, then the dev list
would be a good place to discuss actual approach.
I'll close this for now.
> 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.4.14#64029)
