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:42:21 GMT


Michael Jumper updated GUACAMOLE-5:
    Comment: was deleted

(was: Github user mike-jumper commented on a diff in the pull request:
    --- Diff: extensions/guacamole-auth-jdbc/modules/guacamole-auth-jdbc-base/src/main/java/org/apache/guacamole/auth/jdbc/connection/
    @@ -157,6 +158,12 @@ public void setConfiguration(GuacamoleConfiguration config) {
    +    public Set<String> getSharingProfileIdentifiers()
    --- End diff --
    No, it's just not implemented. These are the API changes only, with the actual implementation
of that API coming later.
    I figured that if I held off on the review of the API until the underlying implementation
was complete, that would distract from the review of the API design itself, and make the PR
way too large.

> 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