[jira] [Reopened] (GUACAMOLE-1428) Save a shared Password when using SSO

["guacamole tester (Jira)" <ji...@apache.org>]

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

guacamole tester reopened GUACAMOLE-1428:
-----------------------------------------

this is not a dublicate of the linked issue.

 

it's not about integrating any external system but to add functionality to the already supported "Enter Password" Feature.

to save this password in Guacamole (like when you save a connection, but make it dynamically and shared (on a user-bases) so as soon as the password is wrong it will be replaced with the newly entered one.)

 

the shared-pw. feature means that it would be great to have an additional option to select which connections share the same password.

 

this way I would be able to launch multiple remote-apps without loading the whole Desktop while only have the cleartext password inside guacamole and still profit from SSO.

> Save a shared Password when using SSO
> -------------------------------------
>
>                 Key: GUACAMOLE-1428
>                 URL: https://issues.apache.org/jira/browse/GUACAMOLE-1428
>             Project: Guacamole
>          Issue Type: New Feature
>          Components: guacamole
>    Affects Versions: 1.3.0
>            Reporter: guacamole tester
>            Priority: Minor
>
> Currently I'm using Guacamole with OIDC-SSO. so I don't have the "${GUAC_PASSWORD}"-Variable at hand.
>  
> The only Option to give the user a true SSO-experience is to integrate an external System which can provide the cleartext-password. I don't like this idea..
> So if it's only possible to do this with a system saving the cleartext password.. why not keep this only in guacamole?
>  
> A working system could be like this:
> when there is no pre-configured Password provide a selectable field that defines that the password for the user is stored. This password should then be stored for all connections (which have the field "shared password" activated) of the user on the guacamole server until it is wrong and then overwritten with the new password that the user enters.
>  
> this would be very easy to implement for the admin as there is no additional configuration. and it would also only keep the password in cleartext ont he guacamole system which in my case is the only system, that needs a cleartext password.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)