682: Cannot login after fresh install under apache http.

sinf****@gmai***** (Google Code) (Is this you? Claim this profile.)
Feb. 10, 2009
I tried the latest svn version and followed the wiki "Getting Started"
steps to install all necessary stuff. I setup reviewboard to work under
apache httpd. But I cannot login. I get the message "cookies must be
enabled". My brwoser has cookies enabled and the following cookie is set
"rbsessionid". Following the installation guide installed django version
1.1.0 alpha on my system.
david
#1 david
Can you try Django 1.0? It seems like there are some issues with 1.1.0 alpha.
  • +NeedInfo
#2 sinf****@gmai***** (Google Code) (Is this you? Claim this profile.)
I tried with version 1.0.0 final and have the same issue.
chipx86
#3 chipx86
Can you provide some information such as your Apache configuration file and your
settings_local.py (remove any sensitive info first)?

What browser are you running, and what extensions are installed?

What OS/distro is this running on?
#4 sinf****@gmai***** (Google Code) (Is this you? Claim this profile.)
<Location "/reviewboard/">
            PythonPath "['/usr/local/src'] + ['/usr/local/src/reviewboard'] +
['/usr/local/src/reviewboard/djblets'] + sys.path"                                  
                                         
            SetEnv DJANGO_SETTINGS_MODULE reviewboard.settings
            SetHandler mod_python
            PythonHandler django.core.handlers.modpython
            PythonAutoReload Off
            PythonDebug Off
            # If you run multiple mod_python sites in the same apache
            # instonce, uncomment this line:
            # PythonInterpreter reviewboard
            AuthName "bla reviewboard"                                              
                                                                                    
                               
            AuthType Basic
            AuthUserFile /etc/apache2/SubversionUsers
            require valid-user
    </Location>
#5 sinf****@gmai***** (Google Code) (Is this you? Claim this profile.)
It is running on linux/Debian.
#6 sinf****@gmai***** (Google Code) (Is this you? Claim this profile.)
# Database backend.  Any supported django database engine should work.
DATABASE_ENGINE = 'mysql'      # 'postgresql', 'mysql', 'sqlite3' or 'ado_mssql'.
DATABASE_NAME = 'reviewboard'  # Or path to database file if using sqlite3.
DATABASE_USER = 'hmm'     # Not used with sqlite3.
DATABASE_PASSWORD = 'hmm' # Not used with sqlite3.
DATABASE_HOST = 'localhost'             # Set to empty string for localhost.
DATABASE_PORT = ''             # Set to empty string for default.

# Make this unique, and don't share it with anybody.
SECRET_KEY = 'secretkey'

# Cache backend.  Unset this to turn off caching completely.  As with most
# django installations, the best option is probably to use memcached.
CACHE_BACKEND = 'locmem:///'

# Local time zone for this installation. All choices can be found here:
#
http://www.postgresql.org/docs/8.1/static/datetime-keywords.html#DATETIME-TIMEZONE-SET-TABLE
TIME_ZONE = 'GMT'

# Language code for this installation. All choices can be found here:
# http://www.w3.org/TR/REC-html40/struct/dirlang.html#langcodes
# http://blogs.law.harvard.edu/tech/stories/storyReader$15
LANGUAGE_CODE = 'en-us'

# This should match the ID of the Site object in the database.  This is used to
# figure out URLs to stick in e-mails and related pages.
SITE_ID = 1

# Set this to the place of your reviewboard if it does not reside
# at the root of your server. - Add the trailing slash.
SITE_ROOT = "/reviewboard/"

# If you set this to False, Django will make some optimizations so as not
# to load the internationalization machinery.
USE_I18N = True


# TLS for LDAP.  If you're using LDAP authentication and your LDAP server
# doesn't support ldaps://, you can enable start-TLS with this.
LDAP_TLS = False

ENABLE_SEARCH = True
david
#7 david
Is this still a problem for you?
#8 Ivan.Y.K********@gmai***** (Google Code) (Is this you? Claim this profile.)
I experience the same problem on Ubuntu 8.04 with Django 1.0.2 final and LDAP
authentication
david
#9 david
This bug isn't about LDAP authentication (which is probably a misconfiguration on
your server), it's about a basic installation with the builtin django authentication.
Since the original poster hasn't replied, I'm going to assume that this is no longer
a problem.
  • -NeedInfo
    +UserError