Displaying 2 results from an estimated 2 matches for "o3tlncaovav48g".
2016 Dec 03
2
SAML | Input buffer full (no auth attempts in 0 secs)
...Note, the actual 'password' is even longer.
This connection attempt is causing dovecot to throw the
following error:
> Dec 02 22:34:33 imap-login: Info: Disconnected: Input buffer full (no
> auth attempts in 0 secs): user=<>, rip=x.y.z.32, lip=x.y.z.68,
> session=<d+o3tLNCaOvAV48g>
and
> BYE Input buffer full, aborting
So this doesn't work. :-(
The question: is there a way to make this work? (make the input buffer
larger, for example..?)
Or any other ideas to make this work?
Thanks in advance,
MJ
2016 Dec 03
0
SAML | Input buffer full (no auth attempts in 0 secs)
...rd".
>
> Watching this (tcpflow) as it happens,i can see the following auth attempt coming from sogo:
..
> > Dec 02 22:34:33 imap-login: Info: Disconnected: Input buffer full (no
> > auth attempts in 0 secs): user=<>, rip=x.y.z.32, lip=x.y.z.68,
> > session=<d+o3tLNCaOvAV48g>
If SOGo used AUTHENTICATE PLAIN instead of LOGIN, it should work. The SASL authentication buffer is larger (8 kB) than regular commands' buffer (~1 kB).
> The question: is there a way to make this work? (make the input buffer larger, for example..?)
You could also increase this:
src/...