[
https://issues.apache.org/jira/browse/GUACAMOLE-221?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15935275#comment-15935275
]
Nick Couchman commented on GUACAMOLE-221:
-----------------------------------------
Oh, and the other thing I forgot about that I'm running into with the
prompting, particularly trying to use ${GUAC_PROMPT} in the current token
setup. There's not really a good way to tell what type of data you're
prompting for. So, presumably if you're going to be prompting for a password
you want to use the password field (especially the part where it hides what
you're typing), and if you're going to be prompting for the port you want a
numeric field that enforces that the selection/input be numeric. Without
significant changes to the current token setup, this isn't really possible -
some minor changes would allow us to pass through the field name that's being
prompted for and make some determination based on that (if field name ==
password, use password field, if field name == port, use numeric field, else
use text field), but I'm not sure that's the cleanest way to go.
> Parameter prompting within client interface
> -------------------------------------------
>
> Key: GUACAMOLE-221
> URL: https://issues.apache.org/jira/browse/GUACAMOLE-221
> Project: Guacamole
> Issue Type: New Feature
> Components: guacamole
> Reporter: Michael Jumper
>
> {panel:bgColor=#FFFFEE}
> *The description of this issue was copied from
> [GUAC-335|https://glyptodon.org/jira/browse/GUAC-335], 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}
> Some parameters, such as the username/password for VNC or RDP, are better
> entered manually within the client when connecting rather than stored on the
> server in MySQL or {{user-mapping.xml}}.
> Storing secure data within parameters on the server side has security
> implications that don't fit well with all use cases.
> Further, some connections would benefit if their settings can be modified
> locally before connecting. A user could change the color depth or screen size
> of their RDP session, for example, for the sake of a slower connection.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
