One thing you may be able to try is this:
1) Run rb-site manage /path/to/site shell
from djblets.siteconfig.models import SiteConfiguration
siteconfig = SiteConfiguration.objects.get_current()
That should properly reset the auth backend to LDAP. As long as you have the
LDAP python module installed, you should be able to use it fine.
Let me know if that works or not.
Christian Hammond - chip...@chipx86.com
Review Board - http://www.review-board.org
VMware, Inc. - http://www.vmware.com
On Mon, Aug 31, 2009 at 3:05 PM, Kash <kashifsal...@gmail.com> wrote:
> How can I change it without changing it on the live server? Can I
> change those settings without logging in to the new server since I
> can't login?
> On Aug 31, 2:33 pm, Christian Hammond <chip...@chipx86.com> wrote:
> > That's the problem, the "accounts.backends.LDAPBackend". That needs to be
> > the full path: "reviewboard.accounts.backends.LDAPBackend."
> > You'll also need to make sure you have the python-ldap package on your
> > system.
> > Christian
> > --
> > Christian Hammond - chip...@chipx86.com
> > Review Board -http://www.review-board.org
> > VMware, Inc. -http://www.vmware.com
> > On Mon, Aug 31, 2009 at 2:18 PM, Kash <kashifsal...@gmail.com> wrote:
> > > Hello Christian,
> > > Actually the original installation is on a different server and it is
> > > using "Custom" authentication method with
> > >
> > > in the Backends field. I didn't want to disturb that installation so I
> > > installed a fresh copy of 1.0.1 and now I am trying to upgrade a copy
> > > of the original database. Maybe this this new server doesn't have this
> > > "backend" thing? I am not exactly sure what it is to begin with. Is
> > > there a way to change the auth type somewhere in the database since I
> > > can't seem to authenticate?
> > > I did restart the webserver and memcached after upgrade.
> > > The original installation is at least at least couple of years old.
> > > Kash
> > > On Aug 31, 1:24 pm, Christian Hammond <chip...@chipx86.com> wrote:
> > > > Hi Kash,
> > > > What login method were you using? Standard auth, or something like
> > > > LDAP/ActiveDirectory?
> > > > How old was your 0.9 install?
> > > > Did you restart your web server after the upgrade?
> > > > I can't think of a thing that changed that would cause auth to fail.
> > > > Christian
> > > > --
> > > > Christian Hammond - chip...@chipx86.com
> > > > Review Board -http://www.review-board.org
> > > > VMware, Inc. -http://www.vmware.com
> > > > On Mon, Aug 31, 2009 at 12:46 PM, Kash <kashifsal...@gmail.com>
> > > > > Hello Folks,
> > > > > I went through the upgrade steps and upgraded reviewboard from 0.9
> > > > > 1.0.1 and in the end ran the command (output also shown)
> > > > > r...@reviewboard:/var/www# rb-site upgrade /var/www/review
> > > > > Rebuilding directory structure
> > > > > Updating database. This may take a while.
> > > > > Upgrading Review Board from 0.9 to 1.0.1
> > > > > There are unapplied evolutions for reviews.
> > > > > There are unapplied evolutions for scmtools.
> > > > > Project signature has changed - an evolution is required
> > > > > Installing json fixture 'initial_data' from
> > > > >
> > > > > Installed 7 object(s) from 1 fixture(s)
> > > > > Evolution could not be simulated, possibly due to raw SQL mutations
> > > > > Evolution successful.
> > > > > That all seems good, doesn't it? But when I go to the webpage and
> > > > > to login I cannot login. I looked in the mysql database and all the
> > > > > users are still there. I even tried to create another superuser
> > > > > the command
> > > > > $ rb-site manage /path/to/site createsuperuser
> > > > > But I still cannot login. Any help would be appreciated.
> > > > > Kash
You received this message because you are subscribed to the Google Groups
To post to this group, send email to email@example.com
To unsubscribe from this group, send email to
For more options, visit this group at