guacamole-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Michael Jumper (JIRA)" <>
Subject [jira] [Issue Comment Deleted] (GUACAMOLE-5) Allow creation of per-connection share links
Date Mon, 08 Aug 2016 20:41:20 GMT


Michael Jumper updated GUACAMOLE-5:
    Comment: was deleted

(was: Github user mike-jumper commented on a diff in the pull request:
    --- Diff: guacamole/src/main/java/org/apache/guacamole/rest/
    @@ -23,19 +23,11 @@
     import org.apache.guacamole.GuacamoleException;
     import org.apache.guacamole.GuacamoleResourceNotFoundException;
     import org.apache.guacamole.GuacamoleSession;
    - * Provides easy access and automatic error handling for retrieval of objects,
    - * such as users, connections, or connection groups. REST API semantics, such
    - * as the special root connection group identifier, are also handled
    - * automatically.
    + * Provides easy access and automatic error handling for retrieval of objects.
    --- End diff --
    I think I can get rid of this entirely, actually ...

> Allow creation of per-connection share links
> --------------------------------------------
>                 Key: GUACAMOLE-5
>                 URL:
>             Project: Guacamole
>          Issue Type: New Feature
>            Reporter: Michael Jumper
>            Assignee: Michael Jumper
>             Fix For: 0.9.10-incubating
> {panel:bgColor=#FFFFEE}
> *The description of this issue was copied from [GUAC-1074|],
an issue in the JIRA instance used by the Guacamole project prior to its acceptance into the
Apache Incubator.*
> Comments, attachments, related issues, and history from prior to acceptance *have not
been copied* and can be found instead at the original issue.
> {panel}
> Depending on connection and user permissions, users should be able to create one-time
share links that allow external or internal users to share active connections.
> Considering that these links may be needed by groups of users, each link should have
the option to be:
> # One-time use
> # Multi-use (lasts until the sharing user disconnects)
> Once a user joins a connection, their presence should be exposed in the interface, and
the owning user should be able to grant/revoke permission to use the keyboard/mouse, kick
individual users, etc.

This message was sent by Atlassian JIRA

View raw message