[jira] [Updated] (GUACAMOLE-1797) Support using private key stored on disk instead of inside the DB

["Mike Jumper (Jira)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/GUACAMOLE-1797?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Mike Jumper updated GUACAMOLE-1797:
-----------------------------------
    Component/s: guacamole-vault
                     (was: guacamole-auth-jdbc)

> Support using private key stored on disk instead of inside the DB
> -----------------------------------------------------------------
>
>                 Key: GUACAMOLE-1797
>                 URL: https://issues.apache.org/jira/browse/GUACAMOLE-1797
>             Project: Guacamole
>          Issue Type: New Feature
>          Components: guacamole-vault
>            Reporter: bendemctl
>            Priority: Major
>
> We are currently setting up guacamole here and I just realised that the connection credentials are stored in plain text in the database. Would it be possible to allow providing a path to the private key on disk (just like ssh_known_hosts) instead of storing it in the database?
> This would allow us to create new connection without requiring access to the private key (just have to known where it's at). It would also allow us to rotate the key directly on the server without having to mess with database updates.
> We also considered GUACAMOLE-426.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)