Re: [SOGo] How to debug "Invalid credentials (0x31) INFO:{"error_code" = 49"

2017-06-13 Thread Tanstaafl 
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)
>>  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 user
>> friendly error message, rather than the cryptic error code?

> Because you can use other LDAP servers or Active Directory for
> authentication.
> They all deliver different error messages.

So, how hard would it be to handle the most popular ones, and default to
the generic error when encountering an unknown one?
-- 
users@sogo.nu
https://inverse.ca/sogo/lists

Re: [SOGo] How to debug "Invalid credentials (0x31) INFO:{"error_code" = 49"

2017-06-10 Thread Christian Mack 
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 "Invalid credentials".
> 
> If this is known, I'm curious why SOGo doesn't just use the user
> friendly error message, rather than the cryptic error code?
> 

Because you can use other LDAP servers or Active Directory for
authentication.
They all deliver different error messages.


Kind regards,
Christian Mack

-- 
Christian Mack
Universität Konstanz
Kommunikations-, Informations-, Medienzentrum (KIM)
Abteilung Basisdienste
78457 Konstanz
+49 7531 88-4416



smime.p7s
Description: S/MIME Cryptographic Signature

Re: [SOGo] How to debug "Invalid credentials (0x31) INFO:{"error_code" = 49"

2017-06-09 Thread Tanstaafl 
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 user
friendly error message, rather than the cryptic error code?
-- 
users@sogo.nu
https://inverse.ca/sogo/lists

Re: [SOGo] How to debug "Invalid credentials (0x31) INFO:{"error_code" = 49"

2017-06-09 Thread Christian Mack 
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 spoke to me
> about a problem.
> 
> May be they did not realise it yet :)
> 
> As far as I know the users can login to all other systems, like WIFI,
> WIKI, PCs etc with the same credentials. The user backend is OpenLdap.
> 
> 
> Any ideas what and how to debug?
> 

Forgot to mention:
* '(0x31) INFO:{"error_code" = 49"' is the  openLDAP error code (hex=31;
dec=49), which means "Invalid credentials".

* "Invalid credentials" messages can also come from attackers, trying to
get in by brute force. => check their IPs.


Kind regards,
Christian Mack

-- 
Christian Mack
Universität Konstanz
Kommunikations-, Informations-, Medienzentrum (KIM)
Abteilung Basisdienste
78457 Konstanz
+49 7531 88-4416



smime.p7s
Description: S/MIME Cryptographic Signature

Re: [SOGo] How to debug "Invalid credentials (0x31) INFO:{"error_code" = 49"

2017-06-09 Thread Christian Mack 
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, 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 to all other systems, like WIFI,
> WIKI, PCs etc with the same credentials. The user backend is OpenLdap.
> 
> 
> Any ideas what and how to debug?
> 

You can find a list of debugging options at:
https://sogo.nu/nc/support/faq/article/how-to-enable-more-verbose-logging-in-sogo-2.html

For LDAP you need
LDAPDebugEnabled = YES;
in your sogo.conf.


Kind regards,
Christian Mack

-- 
Christian Mack
Universität Konstanz
Kommunikations-, Informations-, Medienzentrum (KIM)
Abteilung Basisdienste
78457 Konstanz
+49 7531 88-4416



smime.p7s
Description: S/MIME Cryptographic Signature

[SOGo] How to debug "Invalid credentials (0x31) INFO:{"error_code" = 49"

2017-06-09 Thread 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 spoke to me 
about a problem.


May be they did not realise it yet :)

As far as I know the users can login to all other systems, like WIFI, 
WIKI, PCs etc with the same credentials. The user backend is OpenLdap.



Any ideas what and how to debug?

Thanks and regards . Götz



smime.p7s
Description: S/MIME Cryptographic Signature