-
Notifications
You must be signed in to change notification settings - Fork 106
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Administrative backend #43
Comments
This is implemented in the backend branch:
This is not implemented yet:
Do we want a config administrative backend? What should be the uses for the Config admin tab? |
Great ! Thank you ! For the dashboard (/admin) I was thinking about somthing like this http://imgur.com/RDACS Have you an idea of interesting numbers to put here ? I think we should remove the config tab for now. But in the future it would be interesting if we could configure filez without opening the ".ini" file for things like Look'n'Feel, Limitations, Localisation, etc. |
To summarize the info we should display on the dashboard (I will regularly update this ticket with your comments) :
|
It could be interesting to be able to manually extend the file lifetime of a file. |
TODO : By default, filez should use a random salt string to hash the password. A solution could be to set the salt user attribute everytime a user is created (even if the user comes from LDAP, it will not have any incidence). Then in the password setter function, alter the password with the hash before hashing it. |
Most of the backend is written. Summary of the yet ToDo:
|
I think that "using a random salt string to hash the password by default" is a "must do". I will take care of this |
Password are now salted by default UAPV@a0cc542 |
By being able to manually extend the file lifetime, do you thought of adding a "add a day" link on the admin backend? The best would be to use the date picker jquery widget http://docs.jquery.com/UI/Datepicker http://jqueryui.com/demos/datepicker/ |
Design pass: http://imgur.com/nndfo&Ltw4v&zhAFA |
Depends on #55. |
using a custom algorithm with internal user authentication does not work with the user admin module. There needs to be two different versions of the algorithm. If the algorithm is blank the current system uses: to set password: 'SHA1(CONCAT(:salt,:password))' Checking the password uses the column, setting password uses a bind variable. here is a fix to include a second option "db_password_set_algorithm". If not set, defaults to db_password_algorithm. |
Hey steamraven, thank you very much for your test, your patch and your 2011/5/19 steamraven <
|
Mickael Martin proposed in the ML to add thses stats:
|
The text was updated successfully, but these errors were encountered: