[
https://issues.apache.org/jira/browse/GUACAMOLE-151?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15895025#comment-15895025
]
Michael Jumper commented on GUACAMOLE-151:
------------------------------------------
I do like that idea ... some sort of token like "GUAC_PROMPT" or "GUAC_ASK"
would make a good deal of sense. We'd need to rearrange things significantly to
allow for REST responses similar to those used to prompt for additional
credentials. Somehow, the {{connect()}} call made to the extension handling the
connection would need to be decoupled from the HTTP/WebSocket tunnel, such that
a sort of tunnel reservation could be created via normal REST (producing some
sort of unique token) and then fulfilled with the normal tunnel connect.
Outside of that, much of the facilities necessary for prompting dynamically are
already present and leveraged for the login screen.
Closing as duplicate of GUACAMOLE-221, being the new upstream version of old
[GUAC-335|https://glyptodon.org/jira/browse/GUAC-335].
> Support Prompting for Authenticators
> ------------------------------------
>
> Key: GUACAMOLE-151
> URL: https://issues.apache.org/jira/browse/GUACAMOLE-151
> Project: Guacamole
> Issue Type: New Feature
> Components: guacamole
> Reporter: Nick Couchman
> Priority: Minor
>
> Support interactive authentication prompts for connections. There are
> several reasons for this:
> - Ability to create connections at an administrative level that apply to many
> users.
> - Ability to support RDP NLA authentication/encryption without having to save
> authenticators.
> - Ability to have Guacamole authentication different from connection
> authentication in the above scenarios - no GUAC_USERNAME/PASSWORD passthrough.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
