alexmax / charonauth Goto Github PK

There should be a command-line tool for the administrative side of charonauth maintenance. The only functionality it needs out of the box is threefold:

• Configuration test.
• Create the database schema.
• Create an administrative user.

Perhaps those three should be merged into one. Maybe.

Future things it could support are things like database migrations, but we don't have to worry about that before 1.0.

I am a knucklehead and accidentally posted a milestone as an issue. Github does not allow me to delete issues. Replace me with an actual issue/feature sometime.

There should be a way to post Sitewide annoucements.

Not sure if this should be a popup or a full news blog.

There should be an audit trail of actions in order to make it easy to keep track of changes to users. This will serve two functions:

• Allow an accurate "Last Seen" for a user.
• Audit the actions of a user or operator, to ferret out troublemakers.

This audit trail should keep track of the user, the current IP address of the acting user, the "Before" and "After" data, and the level of the acting user at the time the change was made.

Right now, unit tests are limited to the authentication server and database modules. Test coverage should be MUCH better.before 1.0 hits.

It should be possible to verify an account and reset your password via email.

Currently, the verifier is stored as a salted SHA256 hash, since that's what cocagne/csrp supports out of the box.

The use of a more secure form of hash such as PBKDF2 should be investigated.

Right now, the site enforces that the user's profile name must be the same as their actual username. Torr and I have decided that instead, people should be able to change their profile name's arbitrarily.

As it stands right now, it's impossible to run the authentication server without also running the web server. This makes the web server run needlessly for hosts which are going to run their own registration process.

Please add a flag or something that so that we can disable the web server.

The site has been built with sqlite. It is probably about time that I ensure that the other databases work properly as well.

MySQL/MariaDB are currently blocked by sequelize/sequelize#2070, which is preventing the ENUM field from being created properly. I have not tested Postgres yet.