Status: New
Owner: ----
Labels: Type-Defect Priority-Medium

New issue 1536 by sierragolfoneniner: Enabling Active Directory causes complete lockout (even local superuser cannot log back in)
http://code.google.com/p/reviewboard/issues/detail?id=1536

I can set up a site, create an admin user with a name that I know is
not in my Active Directory, set RB to use AD, then become totally locked
out of that site.

AD doesn't work and the admin login doesn't work anymore.

I have to just delete the site and recreate it using "rb-site
install".

I even tried turning logging on before switching AD logins on and,
well, after I got the generic startup messages (2 lines total) nothing
appeared in the log.

No errors, no failure messages, *nothing at all*.

I can use various LDAP browsers to connect to the domain controller and
browse around, so I figure I don't need encryption or any additional
permissions.



What version are you running?
1.5 beta 1

What's the URL of the page containing the problem?
(internal server)

What steps will reproduce the problem?
1. Create a RB site and set up a local superuser
2. Set the site to use Active Directory for logins.
3. Log out.
4. You will not be able to log back in.

What operating system are you using? What browser?
The site is running on Python 2.5 / Apache 2.2.15 on Windows Server 2008
Standard Edition.
I've tried logging in using both IE7 and Firefox 3.6 on Win XP

Please provide any additional information below.
(none)

--
You received this message because you are listed in the owner
or CC fields of this issue, or because you starred this issue.
You may adjust your issue notification preferences at:
http://code.google.com/hosting/settings

--
You received this message because you are subscribed to the Google Groups 
"reviewboard-issues" group.
To post to this group, send email to reviewboard-iss...@googlegroups.com.
To unsubscribe from this group, send email to 
reviewboard-issues+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/reviewboard-issues?hl=en.

Reply via email to