[
https://issues.apache.org/jira/browse/GUACAMOLE-807?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16858251#comment-16858251
]
Michael Jumper commented on GUACAMOLE-807:
------------------------------------------
Never mind - I think I found the issue. Within LDAP's
{{ConnectionService.java}}:
{code:java}
Connection connection = new SimpleConnection(name, name, config);
{code}
Since {{SimpleConnection}} now takes on the burden of applying parameter
tokens, and automatic application of parameter tokens by {{SimpleConnection}}
is disabled by default for the sake of compatibility with past usages of that
class, this should actually be:
{code:java}
Connection connection = new SimpleConnection(name, name, config, true);
{code}
This wouldn't have been an issue before as the LDAP extension manually applied
the standard tokens.
See GUACAMOLE-524 and [PR
#333|https://github.com/apache/guacamole-client/pull/333].
> RDP NLA and LDAP
> ----------------
>
> Key: GUACAMOLE-807
> URL: https://issues.apache.org/jira/browse/GUACAMOLE-807
> Project: Guacamole
> Issue Type: Bug
> Components: guacamole, guacamole-auth-ldap, guacamole-client
> Affects Versions: 1.1.0
> Reporter: Vieri
> Priority: Major
>
> Both ${GUAC_USERNAME} and ${GUAC_PASSWORD} are not expanded at all when used
> within an LDAP config (no problem with user-mapping.xml).
> I'm using:
>
> {code:java}
> username=${GUAC_USERNAME}
> password=${GUAC_PASSWORD}
> color-depth=24
> domain=DOMAIN
> hostname=10.215.144.50
> security=nla
> ignore-cert=true
> {code}
>
> within a guacConfigParameter object attribute.
> I also tried escaping $ with \, but it didn't change anything.
> The guacd log shows that it's reading "${GUAC_USERNAME}" instead of the
> actual username entered at guacamole-client login.
>
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
