[
https://issues.apache.org/jira/browse/GUACAMOLE-1976?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nick Couchman closed GUACAMOLE-1976.
------------------------------------
Resolution: Implemented
> Add "OPTIONAL" modifier for Tokens
> ----------------------------------
>
> Key: GUACAMOLE-1976
> URL: https://issues.apache.org/jira/browse/GUACAMOLE-1976
> Project: Guacamole
> Issue Type: New Feature
> Components: Documentation, guacamole-client
> Reporter: Nick Couchman
> Assignee: Nick Couchman
> Priority: Minor
> Fix For: 1.7.0
>
>
> The default behavior of Guacamole with respect to Parameter Tokens when a
> token is encountered is either to substitute the value in, if the token is
> defined, or else substitute in the literal string (${UNDEFINED_TOKEN}) when
> it is unknown.
> There are a small handful of situations where it would be useful for a token
> to be optional - in my specific use-case, I have a Guacamole installation
> where I have both SAML-based SSO configured and LDAP, and, in the cases where
> the user logs in via LDAP, I'd like the ${GUAC_PASSWORD} token to be passed
> through to the connection; however, when SAML-based SSO is used, I'd like for
> Guacamole to prompt for the password.
> My proposed way of handling this is to add the "OPTIONAL" modifier to the
> current list of valid modifiers (LOWER and UPPER), so that, when the
> "OPTIONAL" modifier is present, instead of substituting in the literal text
> of the parameter token, it will skip over that token. Thus, for my use-case,
> the result is that, when the GUAC_PASSWORD token is defined, the login will
> happen with that token; when it is undefined, the user will be prompted.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
