[PATCH v3 7/7] wldap32: supply our username as SASL_CB_AUTHNAME too

Dmitry Timoshkov dmitry at baikal.ru
Fri Feb 19 04:46:17 CST 2021


Hans Leidekker <hans at 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

How did it work before? Not providing user name on SASL_CB_USER is clearly
wrong.

-- 
Dmitry.



More information about the wine-devel mailing list