Closed
Bug 791460
Opened 13 years ago
Closed 13 years ago
Make ConnectionManager in ldappool more robust for default configuration
Categories
(Cloud Services :: Server: Core, defect)
Cloud Services
Server: Core
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: c.koke, Unassigned)
Details
Attachments
(1 file)
|
1.09 KB,
patch
|
Details | Diff | Splinter Review |
User Agent: Mozilla/5.0 (X11; Linux x86_64; rv:14.0) Gecko/20100101 Firefox/14.0.1
Build ID: 20120806212620
Steps to reproduce:
I tried to use the user.ldap module for authentication with some default parameters:
[DEFAULT]
debug = True
profile = false
[auth]
allow_new_users = false
backend = services.user.mozilla_ldap.LDAPUser
ldapuri = ldap://localhost
use_tls = false
check_account_state = false
users_root = "ou=Users,dc=localhost"
search_root = "ou=Users,dc=localhost"
...
Actual results:
The server throwed pyhton execetion with this configuration for two reasons:
1) ConnectionManager didn't takes keyword arguments and couldn't handel the profile
2) Since no bind password is given it tries to apply encode to none
I attach a patch that fixes this issus
Expected results:
The server should handle the config ;)
Comment 1•13 years ago
|
||
Whoops, sorry, this got buried in my inbox. Thanks for the patch! I've made some stylistic tweaks and committed it in http://hg.mozilla.org/services/server-core/rev/d25a4558d96b
Status: UNCONFIRMED → RESOLVED
Closed: 13 years ago
Resolution: --- → FIXED
You need to log in
before you can comment on or make changes to this bug.
Description
•