1171: Unable to configure Active Directory/LDAP authentication scheme
- UserError
- Review Board
gregor******@gmai***** (Google Code) (Is this you? Claim this profile.) | |
July 16, 2009 |
What version are you running? Review Board 1.0 RC3 released What's the URL of the page containing the problem? http://*/admin/settings/general/ What steps will reproduce the problem? 1. Select "Active Directory" in the authentication mode line. 2. Try to configure the mode What is the expected output? What do you see instead? The form is not writable. What operating system are you using? What browser? Ubuntu-9.04-server Ubuntu-9.04 / Firefox 3.0.10 Please provide any additional information below.
root@ubuntu:/var/www# rb-site manage reviews test Creating test database... Creating table django_admin_log Creating table auth_permission Creating table auth_group Creating table auth_user Creating table auth_message Creating table django_content_type Creating table django_site Creating table django_session Creating table siteconfig_siteconfiguration Creating table accounts_reviewrequestvisit Creating table accounts_profile Creating table changedescs_changedescription Creating table diffviewer_filediff Creating table diffviewer_diffset Creating table diffviewer_diffsethistory Creating table reviews_group Creating table reviews_defaultreviewer Creating table reviews_screenshot Creating table reviews_reviewrequest Creating table reviews_reviewrequestdraft Creating table reviews_comment Creating table reviews_screenshotcomment Creating table reviews_review Creating table scmtools_tool Creating table scmtools_repository Creating table django_project_version Creating table django_evolution [NOTICE@1245152554.566121] mcm_server_connect():2302: Software caused connection abort Installing baseline version Evolutions in diffviewer baseline: add_parent_diffs Evolutions in reviews baseline: change_descriptions, last_review_timestamp, shipit_count Evolutions in scmtools baseline: bugzilla_url_charfield Installing index for admin.LogEntry model Installing index for auth.Permission model Installing index for auth.Message model Installing index for siteconfig.SiteConfiguration model Installing index for accounts.ReviewRequestVisit model Installing index for diffviewer.FileDiff model Installing index for diffviewer.DiffSet model Installing index for reviews.ReviewRequest model Installing index for reviews.ReviewRequestDraft model Installing index for reviews.Comment model Installing index for reviews.ScreenshotComment model Installing index for reviews.Review model Installing index for scmtools.Repository model Installing index for django_evolution.Evolution model Installing json fixture 'initial_data' from '/usr/local/lib/python2.6/dist-packages/ReviewBoard-1.0rc3-py2.6.egg/reviewboard/scmtools/fixtures'. Installed 6 object(s) from 1 fixture(s) Installing json fixture 'initial_data' from '/usr/local/lib/python2.6/dist-packages/ReviewBoard-1.0rc3-py2.6.egg/reviewboard/scmtools/fixtures'. Installed 6 object(s) from 1 fixture(s) nose.plugins.cover: ERROR: Coverage not available: unable to import coverage module Failure: ImportError (No module named reviews) ... ERROR ====================================================================== ERROR: Failure: ImportError (No module named reviews) ---------------------------------------------------------------------- Traceback (most recent call last): File "/usr/local/lib/python2.6/dist-packages/nose-0.11.1-py2.6.egg/nose/loader.py", line 368, in loadTestsFromName module = resolve_name(addr.module) File "/usr/local/lib/python2.6/dist-packages/nose-0.11.1-py2.6.egg/nose/util.py", line 334, in resolve_name module = __import__('.'.join(parts_copy)) ImportError: No module named reviews ---------------------------------------------------------------------- Ran 1 test in 0.006s FAILED (errors=1)
I think this is symptomatic of a missing python-ldap package, which Active Directory seems to use under the hood. On Win32, I had to add the path to python-ldap to the PATH, so that it could find the dll's it stores there.
Correct. Sorry for the mistake, it's not a issue. Tested in 1.0.