[
https://issues.apache.org/jira/browse/GUACAMOLE-2051?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17949014#comment-17949014
]
Mike Jumper commented on GUACAMOLE-2051:
----------------------------------------
I can't reproduce the problem as specified, and the behavior between 1.5.5 and
1.6.0 appears to be identical. Overall:
* Injection of LDAP attributes via parameter tokens works in both 1.5.5 and
1.6.0 (with the caveat that the specified case of attributes is not respected
in generation of the token - see above).
* Generation of parameter tokens from LDAP attributes works identically whether
those attributes are specified in {{guacamole.properties}} or
{{ldap-servers.yml}}.
There is an issue with naming of tokens, since those tokens are named based on
case within the attribute name and that case is no longer as the administrator
configured, but the tokens are indeed there and that behavior (though a bug) is
not a regression.
> LDAP user attributes do not work when specified in ldap-servers.yml, at all
> with 1.6.0+
> ---------------------------------------------------------------------------------------
>
> Key: GUACAMOLE-2051
> URL: https://issues.apache.org/jira/browse/GUACAMOLE-2051
> Project: Guacamole
> Issue Type: Bug
> Components: guacamole-auth-ldap
> Affects Versions: 1.5.5
> Environment: Docker
> Reporter: sbcbus
> Priority: Major
>
> 2 issues, but both related in the end. It made it a bit difficult to
> troubleshoot due to the variance.
> +In 1.5.5:+
> It seems "user-attributes:" does not work when specified in ldap-servers.yml.
> We recently had a change where we added an additional LDAP source so moved
> the entire config to there. Our connections that rely on custom attributes
> for the connection host name stopped working. *Uncommenting
> ldap-user-attributes: ... in guacamole.properties is a workaround.*
>
> +1.6.0:+
> The attributes do not seem to work *at all* in latest staging/1.6.0 branch.
> ldap-user-attributes: customAttributeName nor specifying it in ldap-users.yml
> as user-attributes: customAttributeName. Guacd logs shows the error as
> incorrect host name/dns error seemingly confirming it not being read.
> Reverting docker back to 1.5.5 results in case above.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
