[
https://issues.apache.org/jira/browse/GUACAMOLE-1648?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18048400#comment-18048400
]
Nick Couchman commented on GUACAMOLE-1648:
------------------------------------------
[~lexaphix] Thanks for the feedback. A couple of notes on this:
* I still haven't really changed by viewpoint on the system-wide
"Administrator" permission being a truly administrative position. This
permission should not be given to anyone you don't trust, as it carries a lot
of weight in the Guacamole system, and I don't know that limiting this one
function - joining an existing connection - makes sense to limit. I suppose I'm
still open to it being a configurable option - for example, a setting in
guacamole.properties - but I believe the default behavior should stay as-is.
* It is possible to create separate permissions on a per-connection basis.
Right now this is only possible by directly manipulating data within the JDBC
module, but the underlying permissions system does support it. GUACAMOLE-1957
actually deals with this, and I've taken an initial stab at a [pull
request|https://github.com/apache/guacamole-client/pull/995] to implement it.
> Asking for permission if admins connect to open session
> -------------------------------------------------------
>
> Key: GUACAMOLE-1648
> URL: https://issues.apache.org/jira/browse/GUACAMOLE-1648
> Project: Guacamole
> Issue Type: Improvement
> Reporter: Igor Sweet
> Priority: Minor
>
> In the Issue GUACAMOLE-1293 a notification for the adminaccess to a session
> is planned to be implemented.
> I think the better way is, to ask a user if he/she consents to share the
> session. This will be more privacy frindly and gives the user more control
> over the session.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
