On Mon, Sep 19, 2016 at 09:50:49AM +0200, Jakub Hrozek wrote:
> On Wed, May 11, 2016 at 12:48:58PM +0200, Jakub Hrozek wrote:
> > master:
> > 8eb4a1f773b6c2246b0a6c6e3c3b8ef4d79c9ca6
> > 73dd89c3fb361dab43b4802510f4c64d282dbde1
>
> I would like to backport these fixes to sssd-1-13..
On Wed, May 11, 2016 at 11:42:40AM +0200, Jakub Hrozek wrote:
> On Wed, May 11, 2016 at 10:24:10AM +0200, Pavel Březina wrote:
> > On 05/10/2016 04:00 PM, Jakub Hrozek wrote:
> > > On Thu, Apr 21, 2016 at 02:54:21PM +0200, Pavel Březina wrote:
> > > > We can fail in sasl_bind_send() with
On Wed, May 11, 2016 at 10:24:10AM +0200, Pavel Březina wrote:
> On 05/10/2016 04:00 PM, Jakub Hrozek wrote:
> > On Thu, Apr 21, 2016 at 02:54:21PM +0200, Pavel Březina wrote:
> > > We can fail in sasl_bind_send() with ERR_AUTH_FAILED for basically
> > > unspecified reason but we do not failover
On 05/10/2016 04:00 PM, Jakub Hrozek wrote:
On Thu, Apr 21, 2016 at 02:54:21PM +0200, Pavel Březina wrote:
We can fail in sasl_bind_send() with ERR_AUTH_FAILED for basically
unspecified reason but we do not failover to next server. This patch should
fix it.
As said on the meeting, I didn't
On Thu, Apr 21, 2016 at 02:54:21PM +0200, Pavel Březina wrote:
> We can fail in sasl_bind_send() with ERR_AUTH_FAILED for basically
> unspecified reason but we do not failover to next server. This patch should
> fix it.
>
> As said on the meeting, I didn't reproduce it and I'm not sure if it will