On Sat Jun 10 2017 03:11:03 GMT-0400 (Eastern Standard Time), Christian
Mack (christian.m...@uni-konstanz.de) wrote:
> Am 09.06.2017 um 15:16 schrieb Tanstaafl (tansta...@libertytrek.org):
>> On 6/9/2017, 8:03:43 AM, Christian Mack (christian.m...@uni-konstanz.de)
>>
Hello
Am 09.06.2017 um 15:16 schrieb Tanstaafl (tansta...@libertytrek.org):
> On 6/9/2017, 8:03:43 AM, Christian Mack (christian.m...@uni-konstanz.de)
> wrote:
>> Forgot to mention:
>> * '(0x31) INFO:{"error_code" = 49"' is the openLDAP error code (hex=31;
>> dec=49), which means
On 6/9/2017, 8:03:43 AM, Christian Mack (christian.m...@uni-konstanz.de)
wrote:
> Forgot to mention:
> * '(0x31) INFO:{"error_code" = 49"' is the openLDAP error code (hex=31;
> dec=49), which means "Invalid credentials".
If this is known, I'm curious why SOGo doesn't just use the
Am 09.06.2017 um 11:37 schrieb Götz Reinicke - IT Koordinator
(goetz.reini...@filmakademie.de):
> Hi,
>
> an user told me he cant login to SOGo and gets an error ""
>
> In the SOGo logs I do see a lot of "Invalid credentials (0x31)
> INFO:{"error_code" = 49" from different users, which never
Hello Götz
Am 09.06.2017 um 11:37 schrieb Götz Reinicke - IT Koordinator
(goetz.reini...@filmakademie.de):
> Hi,
>
> an user told me he cant login to SOGo and gets an error ""
>
> In the SOGo logs I do see a lot of "Invalid credentials (0x31)
> INFO:{"error_code" = 49" from different users,
Hi,
an user told me he cant login to SOGo and gets an error ""
In the SOGo logs I do see a lot of "Invalid credentials (0x31)
INFO:{"error_code" = 49" from different users, which never spoke to me
about a problem.
May be they did not realise it yet :)
As far as I know the users can login