Opened 19 years ago
Closed 18 years ago
#3059 closed defect (invalid)
Assertion with environments which directory names contain hyphens or underscores.
Reported by: | Owned by: | Jonas Borgström | |
---|---|---|---|
Priority: | normal | Milestone: | |
Component: | general | Version: | devel |
Severity: | normal | Keywords: | |
Cc: | Branch: | ||
Release Notes: | |||
API Changes: | |||
Internal Changes: |
Description (last modified by )
After upgrading Trac from one of the 0.9 betas to the current trunk (checked out few days ago) I got following error while trying to login into some of the Trac environments: Python traceback
Traceback (most recent call last): File "/usr/local/lib/python2.4/site-packages/trac/web/modpython_frontend.py", line 206, in handler dispatch_request(mpr.path_info, mpr, env) File "/usr/local/lib/python2.4/site-packages/trac/web/main.py", line 139, in dispatch_request dispatcher.dispatch(req) File "/usr/local/lib/python2.4/site-packages/trac/web/main.py", line 107, in dispatch resp = chosen_handler.process_request(req) File "/usr/local/lib/python2.4/site-packages/trac/web/auth.py", line 80, in process_request self._do_login(req) File "/usr/local/lib/python2.4/site-packages/trac/web/auth.py", line 101, in _do_login assert req.remote_user, 'Authentication information not available.' AssertionError: Authentication information not available.
After speding some time investigatin the matter I found that "problem" environments all have hyphens in the name of their storage directories. That was not a problem with old (one of 0.9bX) version of Trac. I am not completely sure that problem is in Trac and not in other libraries, as they were upgraded too in the process :) My current environment is RHEL AS 4. Python 2.3 (that comes with it), Apache httpd 2.0.52, mod_python 3.1.4, sqlite 3.2.2, pysqlite 1.1.6. The above error message is taken form another server running on SLackware 10.2 with Python 2.4.1 - so it is obviously not a Python problem. Well, I'm getting short of time right now, but will be glad to provide any additional information in case you need it.
Attachments (0)
Change History (6)
comment:1 by , 19 years ago
comment:2 by , 19 years ago
Description: | modified (diff) |
---|---|
Priority: | low → normal |
comment:3 by , 18 years ago
I've been trying to set up authorization on a tracd instance running in a shared hosting environment and have encountered this "Authentication information not available" problem. My home directory on the server contains a hyphen, and several directories in the path to the project contain hyphens or underscores.
Running tracd/0.10dev proxied through apache/2.0.52, python/2.3.4. Redhat CentOS 4.2final
comment:4 by , 18 years ago
After further experimentation, hyphens/underscores seem to have nothing to do with this. I renamed or symlinked hyphen-less names and restarted everything. Still get "assert req.remote_user, 'Authentication information not available.'" error when trying login link.
Running tracd daemon proxied by apache; apache has digest authorization enabled and successfully challenges and passes users using the same digest file as trac's —auth option points at.
comment:5 by , 18 years ago
Devin, it's probably the way you start tracd which is in cause, here. Did you follow carefully the TracStandalone#UsingAuthentication instructions?
comment:6 by , 18 years ago
Resolution: | → invalid |
---|---|
Status: | new → closed |
This was most likely a misconfiguration of the authentication settings.
Refer to TracFaq#WhataboutthisAuthenticationinformationnotavailable.error.
Trac 0.9.5 has this problem also.
It only happens when clicking the "login" button, this problem does not occur if project has forced authentication.