Modify

Opened 8 years ago

Closed 8 years ago

Last modified 3 years ago

#533 closed defect (worksforme)

Upon login, Authentication information not available

Reported by: ch3nyong Owned by: mgood
Priority: high Component: AccountManagerPlugin
Severity: major Keywords:
Cc: Trac Release: 0.10

Description

I had been suffering from following error upon login since few days ago. The database file is fine, and the password file is good. Can anyone enlighten me where should I probably be heading towards to solve this problem? I need urgent help, thanks a million!

Python Traceback
Traceback (most recent call last):
  File "/usr/lib/python2.3/site-packages/trac/web/main.py", line 315, in dispatch_request
    dispatcher.dispatch(req)
  File "/usr/lib/python2.3/site-packages/trac/web/main.py", line 200, in dispatch
    resp = chosen_handler.process_request(req)
  File "/usr/lib/python2.3/site-packages/trac/web/auth.py", line 95, in process_request
    self._do_login(req)
  File "/usr/lib/python2.3/site-packages/trac/web/auth.py", line 116, in _do_login
    assert req.remote_user, 'Authentication information not available.'
AssertionError: Authentication information not available.

Attachments (0)

Change History (6)

comment:1 Changed 8 years ago by ch3nyong

For your information, it was run on tracd and nothing's wrong with apache configuration. Thank you!

comment:2 Changed 8 years ago by ch3nyong

  • Resolution set to fixed
  • Status changed from new to closed
  • Trac Release changed from 0.9 to 0.10

It seemed to be that I was running it on tracd standalone and it differs from running on Apache (where it would rely on Apache's password authentication method)..

Another mistake, I was runnin trac 0.10dev instead of 0.9, and it happened that 0.10 doesnt work well with the TracAccountManager plugin. So, I finally opted for dbauth plugin, which is compatible with trac 0.10, uses sqlite, and it works so magically.

Thanks!

comment:3 Changed 8 years ago by mgood

  • Resolution fixed deleted
  • Status changed from closed to reopened

The fixed resolution should only be used for tickets requiring code changes.

comment:4 Changed 8 years ago by mgood

  • Resolution set to worksforme
  • Status changed from reopened to closed

I guess if you're no longer using the plugin there's no way to debug this so I'll go ahead and close the ticket. The AccountManagerPlugin definitely is supported on Trac 0.10, and I've tested it on both tracd and Apache without problems.

comment:5 follow-up: Changed 8 years ago by mhenry

I was also receiving the same error until I added the following to the components section of my trac.ini:

[components]
trac.web.auth.LoginModule = disabled
...

comment:6 in reply to: ↑ 5 Changed 8 years ago by mgood

Replying to mhenry:

I was also receiving the same error until I added the following to the components section of my trac.ini:

[components]
trac.web.auth.LoginModule = disabled
...

Yes, you need to disable the built-in LoginModule in order to use the AccountManager version. This is already documented: AccountManagerPlugin#LoginModule

Add Comment

Modify Ticket

Action
as closed The owner will remain mgood.
The resolution will be deleted. Next status will be 'reopened'.
Author


E-mail address and user name can be saved in the Preferences.

 
Note: See TracTickets for help on using tickets.