[jira] [Commented] (GUACAMOLE-426) Per-user SSH key

["Nick Couchman (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/GUACAMOLE-426?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16351563#comment-16351563 ] 

Nick Couchman commented on GUACAMOLE-426:
-----------------------------------------

This issue depends on GUACAMOLE-96, which enables the JDBC extension to store arbitrary information for other extensions.  Since that's now implemented (mostly), that should make room for this to continue on - as soon as someone has time to work on it :-).

> Per-user SSH key
> ----------------
>
>                 Key: GUACAMOLE-426
>                 URL: https://issues.apache.org/jira/browse/GUACAMOLE-426
>             Project: Guacamole
>          Issue Type: New Feature
>          Components: guacamole-auth-jdbc
>    Affects Versions: 0.9.13-incubating
>            Reporter: Michael Reber
>            Priority: Minor
>         Attachments: Guacamole_new_feature.png
>
>
> Currently guacamole does not allow having each user with his/her private ssh-key and username defined.
> I was thinking about a possible solution. Briefly, it goes like this: 
> There would be an additional entry in the user settings, where each user can define his/her private ssh-key.  
> There should also be an override option for the current user mapped to a specific server. 
> I attached a possible graphical implementation.  
> Technically, I have the idea to check the following upon each new session opening: 
> If the override option is set and the specific user credentials username and specific ssh-key are valid, then I would replace the default username and the ssh-keys string with the values specified by the user settings.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)