Have the Account Manager be able to use a RDBMS for login authorization

[Eddie Parker]

Hey!

I was on the IRC channel with mgood earlier, and he said that due to the volume of people wishing for the Account Manager to do authorization against a DB using a login form, he'd go ahead and do this. :)

As such, I thought I'd write a ticket so I can find out when it's done so I can integrate it. :)

If I'm to understand correctly, this would involve:

• Have the 'Login' link prompt you for a username password
• Have the backend verify against an RDBMS that you somehow specify.

Obviously feel free to correct my assumptions here, or kill this ticket if you were drunk when you promised this feature (although it would make me rather sad. :)).

[Matt Good]

The form-based authentication is implemented in [132] and [133], but the DB password storage is not yet supported.

To use form authentication the default Trac authentication handler will need to be disabled in trac.ini like:

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

[Lukáš Lalinský]

Component to store user accounts in the database.

[Lukáš Lalinský]

Attached some code to store user names and SHA-encoded passwords in the database.

[Alec Thomas]

database.py by Charlie Clark (out of date)

[Alec Thomas]

I've moved the database.py from the AccountManagerPlugin pagae to here for reference purposes. It no longer works and the one by luks should be used instead I would think.

[John Hampton]

I think that this ticket has been satisfied by the SessionStore password store. Additionally, Account Manager has a well defined API for creating password stores to go against other databases. Examples of these are PhpBbAuthPlugin and TgAuthPlugin