summaryrefslogtreecommitdiffstats
path: root/lib/ASM/DB/Result/User.pm
Commit message (Collapse)AuthorAge
* Revert "Move users to DB"LibravatarJanik Kleinhoff2017-05-08
| | | | | | This reverts commit 7342c7f0e19e15ab3c7ba2133a56393c15989f08. Turns out there are still issues after all.
* Move users to DBLibravatarJanik Kleinhoff2017-05-08
| | | | | | | | | | | | | | | | | | | | | Summary: This will automatically take care of migrating the users from users.json; you may delete that file. Note that this removes htpasswd support. We now store (hashed) user passwords in the database. See T19 for rationale. Test Plan: Run this on a testnet for a while, try to break it. Reviewers: ilbelkyr, #antispammeta Reviewed By: ilbelkyr, #antispammeta Tags: #antispammeta, #database Differential Revision: https://dev.antispammeta.net/D2
* ASM::DB::Result::User: check_passphrase -> check_passwordLibravatarJanik Kleinhoff2016-12-26
| | | | This is for easier integration with Catalyst.
* DB: add "users" table for webusersLibravatarJanik Kleinhoff2016-10-30
For now, mere presence in the table means a given user is authorized to view stuff. We can make this more granular later on (important for T11).