View Issue Details
ID | Project | Category | View Status | Date Submitted | Last Update |
---|---|---|---|---|---|
0002913 | SOGo | Backend General | public | 2014-09-01 13:37 | 2015-01-16 17:57 |
Reporter | Altibox | Assigned To | ludovic | ||
Priority | normal | Severity | minor | Reproducibility | always |
Status | resolved | Resolution | fixed | ||
Platform | [Server] Linux | OS | RHEL/CentOS | OS Version | 6 |
Product Version | 2.2.7 | ||||
Target Version | 2.2.14 | Fixed in Version | 2.2.14 | ||
Summary | 0002913: Login failed due to unhandled error case: -1 | ||||
Description | I am trying to enable ldap passwordPolicy in SOGo. We are currently authentication the users from our RHEL 389 directory server. We want to enable password policy to force to users having stronger passwords. I am curently testing it in our lab environment. | ||||
Steps To Reproduce |
I get 'password change failed' for both.
Now I get: 'Wrong username or password' /var/log/sogo/sogo.log:
I get this message on the login screen when trying to login: /var/log/sogo/sogo.log Any ideas on what is wrong? | ||||
Additional Information | Running RHEL 6.5 on both servers 389-DS server: SOGo server | ||||
Tags | No tags attached. | ||||
We'll have to test it with 389 DS. My guess is that data structures used a while back with OpenLDAP need to be slightly adjusted. |
|
Which openldap libraries are you using? |
|
We are using: openldap-2.4.23-34.el6_5.1.x86_64 |
|
I can reproduce the issue. It seems to be a difference in the way 389 ds works regarding password policies and the control object returned. I'll continue to investigate. |
|
I fixed the login issue. I'll fix the password change with ppolicy enabled tomorrow. 389ds definitively works differently than OpenLDAP regarding ppolicy objects. |
|
The fix for the login was pushed in SOPE. Please update SOPE to test it. Note that your MUST use LDAP over SSL with 389 DS if you want to use the password policy feature. Otherwise, the server will NEVER return the policy control object and things like password changes will never work. The SOGo documentation has been improved in this regard. |
|
Date Modified | Username | Field | Change |
---|---|---|---|
2014-09-01 13:37 | Altibox | New Issue | |
2014-09-02 13:19 | ludovic | Note Added: 0007457 | |
2014-09-05 19:04 | ludovic | Target Version | => 2.2.9 |
2014-09-26 13:37 | ludovic | Target Version | 2.2.9 => 2.2.10 |
2014-11-07 20:41 | ludovic | Target Version | 2.2.10 => 2.2.11 |
2014-12-04 19:30 | ludovic | Target Version | 2.2.11 => 2.2.12 |
2014-12-18 14:38 | ludovic | Target Version | 2.2.12 => 2.2.13 |
2014-12-30 15:28 | ludovic | Target Version | 2.2.13 => 2.2.14 |
2015-01-05 20:33 | ludovic | Note Added: 0007998 | |
2015-01-12 11:22 | Altibox | Note Added: 0008053 | |
2015-01-14 15:56 | ludovic | Note Added: 0008076 | |
2015-01-14 21:20 | ludovic | Note Added: 0008082 | |
2015-01-16 17:57 | ludovic | Note Added: 0008087 | |
2015-01-16 17:57 | ludovic | Status | new => resolved |
2015-01-16 17:57 | ludovic | Fixed in Version | => 2.2.14 |
2015-01-16 17:57 | ludovic | Resolution | open => fixed |
2015-01-16 17:57 | ludovic | Assigned To | => ludovic |