Re: [SOGo] SOGo Web interface Login Failure for some Accounts
http://www.sogo.nu/bugs/view.php?id=2212 Update I could trace the error deeper: I use bindFields = mail, because i haven't found a way to make multi-domain-config logins work with usern...@domain.com login names if there are equal usernames and passwords within different domains, only the first match gets logged in. this creates long usernames, so there was my second approach i created a test user within a different config with a very long username longusername_test-domain-long.com password testtest works password testtest1 shows the same strange behavior every password exceeding 8 chars is creating the strange behavior my conclusion: every combination of user+Password exceeding 41chars will produce this strange behavior with the web interface login screen. could someone confirm this on another machine? -- users@sogo.nu https://inverse.ca/sogo/lists
Re: [SOGo] SOGo Web interface Login Failure for some Accounts
Am 2013-01-29 23:30, schrieb was.besseres.g...@gmx.net:
Every time i try to log in via Web Interface with certain users.
...
First Auth attempt works
Jan 29 23:06:46 sogod [15880]: 0x0x2ab99fc420c8[NGLdapConnection]
Using ldap_init (deprecated) for LDAP host:port 127.0.0.1:389
2013-01-29 23:06:46.753 sogod[15880] -[NGLdapConnection
_searchAtBaseDN:qualifier:attributes:scope:]: search with at base
filter for attrs `h
1.19.158.172 - - [29/Jan/2013:23:06:46 GMT] POST /SOGo/connect
HTTP/1.1 200 27/74 0.023 - - 0
Jan 29 23:06:47 sogod [15880]: 0x0x2ab99f1b13d8[NGLdapConnection]
Using ldap_init (deprecated) for LDAP host:port 127.0.0.1:389
Jan 29 23:06:47 sogod [15880]: 0x0x2ab99f13acd8[LDAPSource]
NSException: 0x2ab99fb50df8 NAME:LDAPException REASON:operation bind
failed: Invalid credentials (0x31) INFO:{login =
uid=some,dc=where,dc=de; }
Jan 29 23:06:47 sogod [15880]:
0x0x2ab99f1b4e38[SOGoWebAuthenticator] tried wrong password for user
'zjWxFWqXYqq73sXtuvpkJXtSWLejQwwWH9PnUe4Ahb9SwY61eb/Fn/h1IxwISRHjEm6eEfZUPZexRhL2WnQ5oQ=='!
Then something goes wrong. I dont even know where this strange string
comes from.
31.19.158.172 - - [29/Jan/2013:23:06:47 GMT] GET /SOGo/s...@where.de
HTTP/1.1 200 4358/0 0.019 12340 64% 0
Then out of nowhere after several serial attempts (around 4 or 5) the
login works and the log shows this.
...
What could be wrong? Why is this phenomen only occurring for certain users?
Auth source is ldap which is working fine with dovecot alone and with
the tb integration. Only the web interface seems to fuzz around.
What SOGo and SOPE Versions do you have installed?
I once hat a similar problem on a test machine where SOGo and SOPE
versions didn't match.
Kind regards,
Christian Mack
--
Christian Mack
Gruppe Informationsdienste
Rechenzentrum Universität Konstanz
--
users@sogo.nu
https://inverse.ca/sogo/lists
Re: [SOGo] SOGo Web interface Login Failure for some Accounts
What SOGo and SOPE Versions do you have installed? It is a CentOS and it is the current version via yum update sogo-2.0.4-1.centos6-x86_64 sope49-mime-4.9-20130125_1664.el6.1-x86_64 sope49-core-4.9-20130125_1664.el6.1-x86_64 sope49-gdl1-contentstore-2.0.4-1.centos6-x86_64 sope49-ldap-4.9-20130125_1664.el6.1-x86_64 sope49-gdl1-postgresql-4.9-20130125_1664.el6.1-x86_64 sope49-sbjson-2.3.1-20130125_1664.el6.1-x86_64 sope49-cards-2.0.4-1.centos6-x86_64 sope49-xml-4.9-20130125_1664.el6.1-x86_64 sope49-appserver-4.9-20130125_1664.el6.1-x86_64 sope49-gdl1-4.9-20130125_1664.el6.1-x86_64 So, i changed the Password (directly via ldap) of the users which were malfunctioning to some short and now i have a contingency: EVERY Password exceeding 11 chars reproduces this strange behavior of the Web interface for any user. Now that is some funny stuff. Every time i get a Jan 30 17:44:48 sogod [29950]: 0x0x2ba843ec0668[SOGoWebAuthenticator] tried wrong password for user 'R7Ljgln4Hf/1aMGXjyubSp1daGfPXfd0VyDGlubGn7VeNmXnsPteFbluGAHWokN8g6s/x6f79c4drqkLbcPwAw=='! Shouldn't there be a real user name and not some b64enc Binary? mfg Hagen -- users@sogo.nu https://inverse.ca/sogo/lists
Re: [SOGo] SOGo Web interface Login Failure for some Accounts
Hello Hagen Am 2013-01-30 17:48, schrieb was.besseres.g...@gmx.net: What SOGo and SOPE Versions do you have installed? It is a CentOS and it is the current version via yum update sogo-2.0.4-1.centos6-x86_64 sope49-mime-4.9-20130125_1664.el6.1-x86_64 sope49-core-4.9-20130125_1664.el6.1-x86_64 sope49-gdl1-contentstore-2.0.4-1.centos6-x86_64 sope49-ldap-4.9-20130125_1664.el6.1-x86_64 sope49-gdl1-postgresql-4.9-20130125_1664.el6.1-x86_64 sope49-sbjson-2.3.1-20130125_1664.el6.1-x86_64 sope49-cards-2.0.4-1.centos6-x86_64 sope49-xml-4.9-20130125_1664.el6.1-x86_64 sope49-appserver-4.9-20130125_1664.el6.1-x86_64 sope49-gdl1-4.9-20130125_1664.el6.1-x86_64 These are OK. So, i changed the Password (directly via ldap) of the users which were malfunctioning to some short and now i have a contingency: EVERY Password exceeding 11 chars reproduces this strange behavior of the Web interface for any user. Now that is some funny stuff. Every time i get a Jan 30 17:44:48 sogod [29950]: 0x0x2ba843ec0668[SOGoWebAuthenticator] tried wrong password for user 'R7Ljgln4Hf/1aMGXjyubSp1daGfPXfd0VyDGlubGn7VeNmXnsPteFbluGAHWokN8g6s/x6f79c4drqkLbcPwAw=='! Shouldn't there be a real user name and not some b64enc Binary? I would suggest to open a bug report at http://www.sogo.nu/bugs for this. Kind regards, Christian Mack -- Christian Mack Gruppe Informationsdienste Rechenzentrum Universität Konstanz -- users@sogo.nu https://inverse.ca/sogo/lists
Re: [SOGo] SOGo Web interface Login Failure for some Accounts
I would suggest to open a bug report at http://www.sogo.nu/bugs for this. Which i did. http://www.sogo.nu/bugs/view.php?id=2212 mfg Hagen -- users@sogo.nu https://inverse.ca/sogo/lists
[SOGo] SOGo Web interface Login Failure for some Accounts
Every time i try to log in via Web Interface with certain users.
Jan 29 23:06:46 sogod [15880]: 0x0x2ab99fd09948[NGLdapConnection]
Using ldap_init (deprecated) for LDAP host:port 127.0.0.1:389
Jan 29 23:06:46 sogod [15880]: 0x0x2ab99f141168[NGLdapConnection]
Using ldap_init (deprecated) for LDAP host:port 127.0.0.1:389
2013-01-29 23:06:46.740 sogod[15880] -[NGLdapConnection
_searchAtBaseDN:qualifier:attributes:scope:]: search with at base
filter for attrs `h
an 29 23:06:46 sogod [15880]: 0x0x2ab99fd09948[NGLdapConnection]
Using ldap_init (deprecated) for LDAP host:port 127.0.0.1:389
Jan 29 23:06:46 sogod [15880]: SOGoRootPage successful login for user
's...@where.de' - expire = -1 grace = -1
First Auth attempt works
Jan 29 23:06:46 sogod [15880]: 0x0x2ab99fc420c8[NGLdapConnection]
Using ldap_init (deprecated) for LDAP host:port 127.0.0.1:389
2013-01-29 23:06:46.753 sogod[15880] -[NGLdapConnection
_searchAtBaseDN:qualifier:attributes:scope:]: search with at base
filter for attrs `h
1.19.158.172 - - [29/Jan/2013:23:06:46 GMT] POST /SOGo/connect
HTTP/1.1 200 27/74 0.023 - - 0
Jan 29 23:06:47 sogod [15880]: 0x0x2ab99f1b13d8[NGLdapConnection]
Using ldap_init (deprecated) for LDAP host:port 127.0.0.1:389
Jan 29 23:06:47 sogod [15880]: 0x0x2ab99f13acd8[LDAPSource]
NSException: 0x2ab99fb50df8 NAME:LDAPException REASON:operation bind
failed: Invalid credentials (0x31) INFO:{login =
uid=some,dc=where,dc=de; }
Jan 29 23:06:47 sogod [15880]:
0x0x2ab99f1b4e38[SOGoWebAuthenticator] tried wrong password for user
'zjWxFWqXYqq73sXtuvpkJXtSWLejQwwWH9PnUe4Ahb9SwY61eb/Fn/h1IxwISRHjEm6eEfZUPZexRhL2WnQ5oQ=='!
Then something goes wrong. I dont even know where this strange string
comes from.
31.19.158.172 - - [29/Jan/2013:23:06:47 GMT] GET /SOGo/s...@where.de
HTTP/1.1 200 4358/0 0.019 12340 64% 0
Then out of nowhere after several serial attempts (around 4 or 5) the
login works and the log shows this.
Jan 29 23:22:19 sogod [15880]: SOGoRootPage successful login for user
's...@where.de' - expire = -1 grace = -1
31.19.158.172 - - [29/Jan/2013:23:22:19 GMT] POST /SOGo/connect
HTTP/1.1 200 27/74 0.007 - - 0
31.19.158.172 - - [29/Jan/2013:23:22:19 GMT] GET /SOGo/s...@where.de
HTTP/1.1 302 0/0 0.003 - - 0
31.19.158.172 - - [29/Jan/2013:23:22:20 GMT] GET
/SOGo/s...@where.de/view HTTP/1.1 302 0/0 0.010 - - 0
31.19.158.172 - - [29/Jan/2013:23:22:20 GMT] GET
/SOGo/so/s...@where.de/Mail HTTP/1.1 302 0/0 0.003 - - 0
31.19.158.172 - - [29/Jan/2013:23:22:21 GMT] GET
/SOGo/so/s...@where.de/Mail/view HTTP/1.1 200 9672/0 0.337 33136 70% 0
31.19.158.172 - - [29/Jan/2013:23:22:23 GMT] POST
/SOGo/so/s...@where.de/Calendar/alarmslist?browserTime=1359498142
HTTP/1.1 200 2/0 0.035 - - 0
31.19.158.172 - - [29/Jan/2013:23:22:23 GMT] POST
/SOGo/so/s...@where.de/Mail/0/mailboxes HTTP/1.1 200 333/0 0.226 - - 0
31.19.158.172 - - [29/Jan/2013:23:22:23 GMT] POST
/SOGo/so/s...@where.de/Mail/1/mailboxes HTTP/1.1 200 333/0 0.299 - - 624K
31.19.158.172 - - [29/Jan/2013:23:22:24 GMT] POST
/SOGo/so/s...@where.de/Mail/2/mailboxes HTTP/1.1 200 333/0 0.285 - - 536K
31.19.158.172 - - [29/Jan/2013:23:22:25 GMT] POST
/SOGo/so/s...@where.de/Mail/3/mailboxes HTTP/1.1 200 333/0 0.285 - - 576K
What could be wrong? Why is this phenomen only occurring for certain users?
Auth source is ldap which is working fine with dovecot alone and with
the tb integration. Only the web interface seems to fuzz around.
mfg Hagen
--
users@sogo.nu
https://inverse.ca/sogo/lists
