[
https://issues.apache.org/jira/browse/GUACAMOLE-2051?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17954429#comment-17954429
]
Mike Jumper commented on GUACAMOLE-2051:
----------------------------------------
[~stcbus] OK, for {{ldap-servers.yml}}, specifying multiple attributes needs to
be done with a list:
{code:none}
user-attributes:
- OSUrdpWS01
- OSUrdpWS02
- OSUrdpWS03
- cn
{code}
Specifying this in {{ldap-servers.yml}} as a single comma-delimited string will
result in that value being used as the name of the attribute. This isn't new
behavior, but isn't clear in the docs.
As for {{guacamole.properties}}, this is a regression resulting from a refactor
that introduced general support for parsing properties as lists. That support
defaults to using semicolons as delimiters, which differs from the commas
normally used by the property. We'll have to go through this and any other
cases that should use commas and correct this.
> 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)
