[
https://issues.apache.org/jira/browse/GUACAMOLE-2051?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17951229#comment-17951229
]
sbcbus edited comment on GUACAMOLE-2051 at 5/13/25 4:25 PM:
------------------------------------------------------------
[~mjumper] any tips or idea? I also tried adding the following:
{code:java}
String attrText = attrList.toString();
logger.info("LDAP: attrText: \"{}\"", attrText); {code}
after
logger.info("LDAP: Getting user attributes...");
Collection<String> attrList = config.getAttributes();
and didn't see that out in the log (same output as I got in previous comment).
I see since 1.5.5 some things changed to 'collections'.
was (Author: JIRAUSER299297):
[~mjumper] any tips or idea? I also tried adding the following:
{code:java}
String attrText = attrList.toString();
logger.info("LDAP: attrText: \"{}\"", attrText); {code}
after
logger.info("LDAP: Getting user attributes...");
and didn't see that out in the log (same output as I got in previous comment).
I see since 1.5.5 some things changed to 'collections'.
> 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)
