[
https://issues.apache.org/jira/browse/GUACAMOLE-426?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Reber updated GUACAMOLE-426:
------------------------------------
Summary: New Feature: Per user ssh-key (was: New Guacamole Feature: Per
user ssh-key)
> New Feature: Per user ssh-key
> -----------------------------
>
> Key: GUACAMOLE-426
> URL: https://issues.apache.org/jira/browse/GUACAMOLE-426
> Project: Guacamole
> Issue Type: Improvement
> Reporter: Michael Reber
> 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
(v6.4.14#64029)
