From: Hans Leidekker <hans@codeweavers.com>
Subject: Re: [PATCH v3 7/7] wldap32: supply our username as SASL_CB_AUTHNAME too
Message-Id: <1608c3f10aec62dbf5ec7a78474e7df82fea4892.camel@codeweavers.com>
Date: Fri, 19 Feb 2021 11:35:19 +0100
In-Reply-To: <20210219132037.09a6b20bf83247dc5ed6f9e6@baikal.ru>
References: <CAJm2B-=uzRw3aH5Q+j6hkUK_CJXPY_UOA7eTiiJ8oL84iVjssQ@mail.gmail.com> <e9e8e51fda5d5722d6afe586d69d3059e7f391af.camel@codeweavers.com> <20210219132037.09a6b20bf83247dc5ed6f9e6@baikal.ru>

On Fri, 2021-02-19 at 13:20 +0300, Dmitry Timoshkov wrote:
> Hans Leidekker <hans@codeweavers.com> wrote:
> 
> > On Thu, 2021-02-18 at 18:50 +0200, Damjan Jovanovic wrote:
> > > Try 3 gives up the attempt to provide credentials in an
> > > authentication method specific form, and just provides our
> > > username as the authentication username (SASL_CB_AUTHNAME) too.
> > 
> > It doesn't work here. This clearly depends on the mechanism used,
> > so I think the previous approach was better.
> 
> Could you provide more details? What doesn't work? What kind of
> authentication method and LDAP server are you using? Does adding
> KRB5_TRACE reveal anything?

GSSAPI and standard AD server. More details here:
https://www.winehq.org/pipermail/wine-devel/2021-January/179973.html