[
https://issues.apache.org/jira/browse/GUACAMOLE-938?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17023414#comment-17023414
]
Mike Jumper commented on GUACAMOLE-938:
---------------------------------------
IIRC, there was a known issue with 1.0.0 which caused referrals to fail for
different reasons, and it was expected that GUACAMOLE-234 would solve that. It
_almost_ does; there's just an issue with the connection process, probably due
to the way the referral connection process is completely distinct from the
generic connection process implemented by {{bindAs()}}.
I'll refactor that a bit such that {{bindAs()}} forms the basis of absolutely
all LDAP connections. That should make things easier to verify.
> Referral following fails when enabled for LDAP
> ----------------------------------------------
>
> Key: GUACAMOLE-938
> URL: https://issues.apache.org/jira/browse/GUACAMOLE-938
> Project: Guacamole
> Issue Type: Bug
> Components: guacamole-auth-ldap
> Affects Versions: 1.0.0, 1.1.0
> Reporter: Mike Jumper
> Priority: Critical
> Fix For: 1.1.0
>
>
> When the {{ldap-follow-referrals}} property is set to {{true}}, it is
> expected that LDAP searches performed by Guacamole will automatically follow
> any received referrals. This occurs, but only partially, with the LDAP
> support not actually initiating an LDAP bind for connections related to
> referrals. Lacking a bind, LDAP servers will tend to refuse the attempt to
> search, and the referral fails.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
